Method and apparatus for performing sl drx operation in nr v2x

ABSTRACT

A method for performing wireless communication by a first device and a device for supporting same are provided. The method may comprise: obtaining a default sidelink (SL) discontinuous reception (DRX) configuration; obtaining a profile representing whether SL DRX is compatible; performing first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establishing a PC5 radio resource control (RRC) connection with a second device; obtaining an SL DRX configuration; transmitting, to the second device, information related to the SL DRX configuration; and performing, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.

CROSS-REFERENCE TO RELATED APPLICATIONS

Pursuant to 35 U.S.C. § 119 (e), this application claims the benefit of U.S. Provisional Application No. 63/229,995 filed on Aug. 5, 2021, the contents of which are hereby incorporated by reference herein in their entirety.

TECHNICAL FIELD

This disclosure relates to a wireless communication system.

BACKGROUND

Sidelink (SL) communication is a communication scheme in which a direct link is established between User Equipments (UEs) and the UEs exchange voice and data directly with each other without intervention of an evolved Node B (eNB). SL communication is under consideration as a solution to the overhead of an eNB caused by rapidly increasing data traffic. Vehicle-to-everything (V2X) refers to a communication technology through which a vehicle exchanges information with another vehicle, a pedestrian, an object having an infrastructure (or infra) established therein, and so on. The V2X may be divided into 4 types, such as vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-network (V2N), and vehicle-to-pedestrian (V2P). The V2X communication may be provided via a PC5 interface and/or Uu interface.

Meanwhile, as a wider range of communication devices require larger communication capacities, the need for mobile broadband communication that is more enhanced than the existing Radio Access Technology (RAT) is rising. Accordingly, discussions are made on services and user equipment (UE) that are sensitive to reliability and latency. And, a next generation radio access technology that is based on the enhanced mobile broadband communication, massive Machine Type Communication (MTC), Ultra-Reliable and Low Latency Communication (URLLC), and so on, may be referred to as a new radio access technology (RAT) or new radio (NR). Herein, the NR may also support vehicle-to-everything (V2X) communication.

FIG. 1 is a drawing for describing V2X communication based on NR, compared to V2X communication based on RAT used before NR. The embodiment of FIG. 1 may be combined with various embodiments of the present disclosure.

Regarding V2X communication, a scheme of providing a safety service, based on a V2X message such as Basic Safety Message (BSM), Cooperative Awareness Message (CAM), and Decentralized Environmental Notification Message (DENM) is focused in the discussion on the RAT used before the NR. The V2X message may include position information, dynamic information, attribute information, or the like. For example, a UE may transmit a periodic message type CAM and/or an event triggered message type DENM to another UE.

Thereafter, regarding V2X communication, various V2X scenarios are proposed in NR. For example, the various V2X scenarios may include vehicle platooning, advanced driving, extended sensors, remote driving, or the like.

SUMMARY

Meanwhile, when the UE #X (e.g., TX UE) and the UE #Y (e.g., RX UE) are performing unicast-based SL communication, the UE #X may simultaneously perform other SL communication with the UE #Z. Under this situation, when the UE #X determines/configures an SL DRX configuration of the UE #Y, the UE #X can minimize its own battery consumption by considering not only a generation pattern of a packet to be transmitted to the UE #Y but also a generation pattern of a packet to be transmitted to the UE #Z. For example, the UE #X may perform packet transmission to the UE #Y and the UE #Z as continuously as possible after turning on its RF, and through this, the UE #X can minimize its own battery consumption. Meanwhile, for example, after the UE #X establishes a unicast link with the UE #Y, if packet transmission from the UE #X to the UE #Y is performed based on an SL DRX configuration related to information such as a TX profile (and/or a QoS profile) related to a packet, not performed based on an SL DRX configuration related to the unicast link, battery consumption minimization in terms of the UE #X (described above) may not be achieved.

In one embodiment, provided may be a method for performing wireless communication by a first device. The method may comprise: obtaining a default sidelink (SL) discontinuous reception (DRX) configuration; obtaining a profile representing whether SL DRX is compatible; performing first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establishing a PC5 radio resource control (RRC) connection with a second device; obtaining an SL DRX configuration; transmitting, to the second device, information related to the SL DRX configuration; and performing, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.

In one embodiment, provided may be a first device adapted to perform wireless communication. The first device may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible; control the one or more transceivers to perform first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establish a PC5 radio resource control (RRC) connection with a second device; obtain an SL DRX configuration; control the one or more transceivers to transmit, to the second device, information related to the SL DRX configuration; and control the one or more transceivers to perform, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.

In one embodiment, provided may be a processing device adapted to control a first device performing wireless communication. The processing device may comprise: one or more processors; and one or more memories operably connected to the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible; perform first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establish a PC5 radio resource control (RRC) connection with a second device; obtain an SL DRX configuration; transmit, to the second device, information related to the SL DRX configuration; and perform, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.

It is possible to maximize the power saving gain of the UE.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a drawing for describing V2X communication based on NR, compared to V2X communication based on RAT used before NR.

FIG. 2 shows a structure of an NR system, based on an embodiment of the present disclosure.

FIG. 3 shows a radio protocol architecture, based on an embodiment of the present disclosure.

FIG. 4 shows a structure of a radio frame of an NR, based on an embodiment of the present disclosure.

FIG. 5 shows a structure of a slot of an NR frame, based on an embodiment of the present disclosure.

FIG. 6 shows an example of a BWP, based on an embodiment of the present disclosure.

FIG. 7 shows a UE performing V2X or SL communication, based on an embodiment of the present disclosure.

FIG. 8 shows a procedure of performing V2X or SL communication by a UE based on a transmission mode, based on an embodiment of the present disclosure.

FIG. 9 shows three cast types, based on an embodiment of the present disclosure.

FIG. 10 shows a method for a first device to perform wireless communication, based on an embodiment of the present disclosure.

FIG. 11 shows a method for a second device to perform wireless communication, based on an embodiment of the present disclosure.

FIG. 12 shows a communication system 1, based on an embodiment of the present disclosure.

FIG. 13 shows wireless devices, based on an embodiment of the present disclosure.

FIG. 14 shows a signal process circuit for a transmission signal, based on an embodiment of the present disclosure.

FIG. 15 shows another example of a wireless device, based on an embodiment of the present disclosure.

FIG. 16 shows a hand-held device, based on an embodiment of the present disclosure.

FIG. 17 shows a vehicle or an autonomous vehicle, based on an embodiment of the present disclosure.

DETAILED DESCRIPTION

In the present specification. “A or B” may mean “only A”, “only B” or “both A and B.” In other words, in the present specification, “A or B” may be interpreted as “A and/or B”. For example, in the present specification, “A, B, or C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, C”.

A slash (/) or comma used in the present specification may mean “and/or”. For example, “A/B” may mean “A and/or B”. Accordingly, “A/B” may mean “only A”, “only B”, or “both A and B”. For example, “A, B, C” may mean “A, B, or C”.

In the present specification, “at least one of A and B” may mean “only A”, “only B”, or “both A and B”. In addition, in the present specification, the expression “at least one of A or B” or “at least one of A and/or B” may be interpreted as “at least one of A and B”.

In addition, in the present specification, “at least one of A, B, and C” may mean “only A”, “only B”, “only C”, or “any combination of A, B, and C”. In addition, “at least one of A, B, or C” or “at least one of A, B, and/or C” may mean “at least one of A, B, and C”.

In addition, a parenthesis used in the present specification may mean “for example”. Specifically, when indicated as “control information (PDCCH)”, it may mean that “PDCCH” is proposed as an example of the “control information”. In other words, the “control information” of the present specification is not limited to “PDCCH”, and “PDCCH” may be proposed as an example of the “control information”. In addition, when indicated as “control information (i.e., PDCCH)”, it may also mean that “PDCCH” is proposed as an example of the “control information”.

A technical feature described individually in one figure in the present specification may be individually implemented, or may be simultaneously implemented.

The technology described below may be used in various wireless communication systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), and so on. The CDMA may be implemented with a radio technology, such as universal terrestrial radio access (UTRA) or CDMA-2000. The TDMA may be implemented with a radio technology, such as global system for mobile communications (GSM)/general packet ratio service (GPRS)/enhanced data rate for GSM evolution (EDGE). The OFDMA may be implemented with a radio technology, such as institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, evolved UTRA (E-UTRA), and so on. IEEE 802.16m is an evolved version of IEEE 802.16e and provides backward compatibility with a system based on the IEEE 802.16e. The UTRA is part of a universal mobile telecommunication system (UMTS). 3rd generation partnership project (3GPP) long term evolution (LTE) is part of an evolved UMTS (E-UMTS) using the E-UTRA. The 3GPP LTE uses the OFDMA in a downlink and uses the SC-FDMA in an uplink. LTE-advanced (LTE-A) is an evolution of the LTE.

5G NR is a successive technology of LTE-A corresponding to a new Clean-slate type mobile communication system having the characteristics of high performance, low latency, high availability, and so on. 5G NR may use resources of all spectrum available for usage including low frequency bands of less than 1 GHz, middle frequency bands ranging from 1 GHz to 10 GHz, high frequency (millimeter waves) of 24 GHz or more, and so on.

For clarity in the description, the following description will mostly focus on LTE-A or 5G NR. However, technical features according to an embodiment of the present disclosure will not be limited only to this.

FIG. 2 shows a structure of an NR system, based on an embodiment of the present disclosure. The embodiment of FIG. 2 may be combined with various embodiments of the present disclosure.

Referring to FIG. 2 , a next generation-radio access network (NG-RAN) may include a BS 20 providing a UE 10 with a user plane and control plane protocol termination. For example, the BS 20 may include a next generation-Node B (gNB) and/or an evolved-NodeB (eNB). For example, the UE 10 may be fixed or mobile and may be referred to as other terms, such as a mobile station (MS), a user terminal (UT), a subscriber station (SS), a mobile terminal (MT), wireless device, and so on. For example, the BS may be referred to as a fixed station which communicates with the UE 10 and may be referred to as other terms, such as a base transceiver system (BTS), an access point (AP), and so on.

The embodiment of FIG. 2 exemplifies a case where only the gNB is included. The BSs 20 may be connected to one another via Xn interface. The BS 20 may be connected to one another via 5th generation (5G) core network (5GC) and NG interface. More specifically, the BSs 20 may be connected to an access and mobility management function (AMF) 30 via NG-C interface, and may be connected to a user plane function (UPF) 30 via NG-U interface.

Layers of a radio interface protocol between the UE and the network can be classified into a first layer (layer 1, L1), a second layer (layer 2, L2), and a third layer (layer 3, L3) based on the lower three layers of the open system interconnection (OSI) model that is well-known in the communication system. Among them, a physical (PHY) layer belonging to the first layer provides an information transfer service by using a physical channel, and a radio resource control (RRC) layer belonging to the third layer serves to control a radio resource between the UE and the network. For this, the RRC layer exchanges an RRC message between the UE and the BS.

FIG. 3 shows a radio protocol architecture, based on an embodiment of the present disclosure. The embodiment of FIG. 3 may be combined with various embodiments of the present disclosure. Specifically. (a) of FIG. 3 shows a radio protocol stack of a user plane for Uu communication, and (b) of FIG. 3 shows a radio protocol stack of a control plane for Uu communication. (c) of FIG. 3 shows a radio protocol stack of a user plane for SL communication, and (d) of FIG. 3 shows a radio protocol stack of a control plane for SL communication.

Referring to FIG. 3 , a physical layer provides an upper layer with an information transfer service through a physical channel. The physical layer is connected to a medium access control (MAC) layer which is an upper layer of the physical layer through a transport channel. Data is transferred between the MAC layer and the physical layer through the transport channel. The transport channel is classified according to how and with what characteristics data is transmitted through a radio interface.

Between different physical layers, i.e., a physical layer of a transmitter and a physical layer of a receiver, data are transferred through the physical channel. The physical channel is modulated using an orthogonal frequency division multiplexing (OFDM) scheme, and utilizes time and frequency as a radio resource.

The MAC layer provides services to a radio link control (RLC) layer, which is a higher layer of the MAC layer, via a logical channel. The MAC layer provides a function of mapping multiple logical channels to multiple transport channels. The MAC layer also provides a function of logical channel multiplexing by mapping multiple logical channels to a single transport channel. The MAC layer provides data transfer services over logical channels.

The RLC layer performs concatenation, segmentation, and reassembly of Radio Link Control Service Data Unit (RLC SDU). In order to ensure diverse quality of service (QoS) required by a radio bearer (RB), the RLC layer provides three types of operation modes, i.e., a transparent mode (TM), an unacknowledged mode (UM), and an acknowledged mode (AM). An AM RLC provides error correction through an automatic repeat request (ARQ).

A radio resource control (RRC) layer is defined only in the control plane. The RRC layer serves to control the logical channel, the transport channel, and the physical channel in association with configuration, reconfiguration and release of RBs. The RB is a logical path provided by the first layer (i.e., the physical layer or the PHY layer) and the second layer (i.e., a MAC layer, an RLC layer, a packet data convergence protocol (PDCP) layer, and a service data adaptation protocol (SDAP) layer) for data delivery between the UE and the network.

Functions of a packet data convergence protocol (PDCP) layer in the user plane include user data delivery, header compression, and ciphering. Functions of a PDCP layer in the control plane include control-plane data delivery and ciphering/integrity protection.

A service data adaptation protocol (SDAP) layer is defined only in a user plane. The SDAP layer performs mapping between a Quality of Service (QoS) flow and a data radio bearer (DRB) and QoS flow ID (QFI) marking in both DL and UL packets.

The configuration of the RB implies a process for specifying a radio protocol layer and channel properties to provide a particular service and for determining respective detailed parameters and operations. The RB can be classified into two types, i.e., a signaling RB (SRB) and a data RB (DRB). The SRB is used as a path for transmitting an RRC message in the control plane. The DRB is used as a path for transmitting user data in the user plane.

When an RRC connection is established between an RRC layer of the UE and an RRC layer of the E-UTRAN, the UE is in an RRC_CONNECTED state, and, otherwise, the UE may be in an RRC_IDLE state. In case of the NR, an RRC_INACTIVE state is additionally defined, and a UE being in the RRC_INACTIVE state may maintain its connection with a core network whereas its connection with the BS is released.

Data is transmitted from the network to the UE through a downlink transport channel. Examples of the downlink transport channel include a broadcast channel (BCH) for transmitting system information and a downlink-shared channel (SCH) for transmitting user traffic or control messages. Traffic of downlink multicast or broadcast services or the control messages can be transmitted on the downlink-SCH or an additional downlink multicast channel (MCH). Data is transmitted from the UE to the network through an uplink transport channel. Examples of the uplink transport channel include a random access channel (RACH) for transmitting an initial control message and an uplink SCH for transmitting user traffic or control messages.

Examples of logical channels belonging to a higher channel of the transport channel and mapped onto the transport channels include a broadcast channel (BCCH), a paging control channel (PCCH), a common control channel (CCCH), a multicast control channel (MCCH), a multicast traffic channel (MTCH), etc.

FIG. 4 shows a structure of a radio frame of an NR, based on an embodiment of the present disclosure. The embodiment of FIG. 4 may be combined with various embodiments of the present disclosure.

Referring to FIG. 4 , in the NR, a radio frame may be used for performing uplink and downlink transmission. A radio frame has a length of 10 ms and may be defined to be configured of two half-frames (HFs). A half-frame may include five 1 ms subframes (SFs). A subframe (SF) may be divided into one or more slots, and the number of slots within a subframe may be determined based on subcarrier spacing (SCS). Each slot may include 12 or 14 OFDM(A) symbols according to a cyclic prefix (CP).

In case of using a normal CP, each slot may include 14 symbols. In case of using an extended CP, each slot may include 12 symbols. Herein, a symbol may include an OFDM symbol (or CP-OFDM symbol) and a Single Carrier-FDMA (SC-FDMA) symbol (or Discrete Fourier Transform-spread-OFDM (DFT-s-OFDM) symbol).

Table 1 shown below represents an example of a number of symbols per slot (N^(slot) _(symb)), a number slots per frame (N^(frame,u) _(slot)), and a number of slots per subframe (N^(subframe,u) _(slot)) based on an SCS configuration (u), in a case where a normal CP is used.

TABLE 1 SCS (15*2^(u)) N^(slot) _(symb) N^(frame, u) _(slot) N^(subframe, u) _(slot) 15 KHz (u = 0) 14 10 1 30 KHz (u = 1) 14 20 2 60 KHz (u = 2) 14 40 4 120 KHz (u = 3) 14 80 8 240 KHz (u = 4) 14 160 16

Table 2 shows an example of a number of symbols per slot, a number of slots per frame, and a number of slots per subframe based on the SCS, in a case where an extended CP is used.

TABLE 2 SCS (15*2^(u)) N^(slot) _(symb) N^(frame, u) _(slot) N^(subframe, u) _(slot) 60 KHz (u = 2) 12 40 4

In an NR system, OFDM(A) numerologies (e.g., SCS, CP length, and so on) between multiple cells being integrate to one UE may be differently configured. Accordingly, a (absolute time) duration (or section) of a time resource (e.g., subframe, slot or TTI) (collectively referred to as a time unit (TU) for simplicity) being configured of the same number of symbols may be differently configured in the integrated cells.

In the NR, multiple numerologies or SCSs for supporting diverse 5G services may be supported. For example, in case an SCS is 15 kHz, a wide area of the conventional cellular bands may be supported, and, in case an SCS is 30 kHz/60 kHz a dense-urban, lower latency, wider carrier bandwidth may be supported. In case the SCS is 60 kHz or higher, a bandwidth that is greater than 24.25 GHz may be used in order to overcome phase noise.

An NR frequency band may be defined as two different types of frequency ranges. The two different types of frequency ranges may be FR1 and FR2. The values of the frequency ranges may be changed (or varied), and, for example, the two different types of frequency ranges may be as shown below in Table 3. Among the frequency ranges that are used in an NR system, FR1 may mean a “sub 6 GHz range”, and FR2 may mean an “above 6 GHz range” and may also be referred to as a millimeter wave (mmW).

TABLE 3 Frequency Range Corresponding Subcarrier Spacing designation frequency range (SCS) FR1  450 MHz-6000 MHz  15, 30, 60 kHz FR2 24250 MHz-52600 MHz 60, 120, 240 kHz

As described above, the values of the frequency ranges in the NR system may be changed (or varied). For example, as shown below in Table 4, FR1 may include a band within a range of 410 MHz to 7125 MHz. More specifically, FR1 may include a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher. For example, a frequency band of 6 GHz (or 5850, 5900, 5925 MHz, and so on) and higher being included in FR1 mat include an unlicensed band. The unlicensed band may be used for diverse purposes, e.g., the unlicensed band for vehicle-specific communication (e.g., automated driving).

TABLE 4 Frequency Range Corresponding Subcarrier Spacing designation frequency range (SCS) FR1  410 MHz-7125 MHz  15, 30, 60 kHz FR2 24250 MHz-52600 MHz 60, 120, 240 kHz

FIG. 5 shows a structure of a slot of an NR frame, based on an embodiment of the present disclosure. The embodiment of FIG. 5 may be combined with various embodiments of the present disclosure.

Referring to FIG. 5 , a slot includes a plurality of symbols in a time domain. For example, in case of a normal CP, one slot may include 14 symbols. However, in case of an extended CP, one slot may include 12 symbols. Alternatively, in case of a normal CP, one slot may include 7 symbols. However, in case of an extended CP, one slot may include 6 symbols.

A carrier includes a plurality of subcarriers in a frequency domain. A Resource Block (RB) may be defined as a plurality of consecutive subcarriers (e.g., 12 subcarriers) in the frequency domain. A Bandwidth Part (BWP) may be defined as a plurality of consecutive (Physical) Resource Blocks ((P)RBs) in the frequency domain, and the BWP may correspond to one numerology (e.g., SCS, CP length, and so on). A carrier may include a maximum of N number BWPs (e.g., 5 BWPs). Data communication may be performed via an activated BWP. Each element may be referred to as a Resource Element (RE) within a resource grid and one complex symbol may be mapped to each element.

Hereinafter, a bandwidth part (BWP) and a carrier will be described.

The BWP may be a set of consecutive physical resource blocks (PRBs) in a given numerology. The PRB may be selected from consecutive sub-sets of common resource blocks (CRBs) for the given numerology on a given carrier

For example, the BWP may be at least any one of an active BWP, an initial BWP, and/or a default BWP. For example, the UE may not monitor downlink radio link quality in a DL BWP other than an active DL BWP on a primary cell (PCell). For example, the UE may not receive PDCCH, physical downlink shared channel (PDSCH), or channel state information-reference signal (CSI-RS) (excluding RRM) outside the active DL BWP. For example, the UE may not trigger a channel state information (CSI) report for the inactive DL BWP. For example, the UE may not transmit physical uplink control channel (PUCCH) or physical uplink shared channel (PUSCH) outside an active UL BWP. For example, in a downlink case, the initial BWP may be given as a consecutive RB set for a remaining minimum system information (RMSI) control resource set (CORESET) (configured by physical broadcast channel (PBCH)). For example, in an uplink case, the initial BWP may be given by system information block (SIB) for a random access procedure. For example, the default BWP may be configured by a higher layer. For example, an initial value of the default BWP may be an initial DL BWP. For energy saving, if the UE fails to detect downlink control information (DCI) during a specific period, the UE may switch the active BWP of the UE to the default BWP.

Meanwhile, the BWP may be defined for SL. The same SL BWP may be used in transmission and reception. For example, a transmitting UE may transmit an SL channel or an SL signal on a specific BWP, and a receiving UE may receive the SL channel or the SL signal on the specific BWP. In a licensed carrier, the SL BWP may be defined separately from a Uu BWP, and the SL BWP may have configuration signaling separate from the Uu BWP. For example, the UE may receive a configuration for the SL BWP from the BS/network. For example, the UE may receive a configuration for the Uu BWP from the BS/network. The SL BWP may be (pre-)configured in a carrier with respect to an out-of-coverage NR V2X UE and an RRC_IDLE UE. For the UE in the RRC_CONNECTED mode, at least one SL BWP may be activated in the carrier.

FIG. 6 shows an example of a BWP, based on an embodiment of the present disclosure. The embodiment of FIG. 6 may be combined with various embodiments of the present disclosure. It is assumed in the embodiment of FIG. 6 that the number of BWPs is 3.

Referring to FIG. 6 , a common resource block (CRB) may be a carrier resource block numbered from one end of a carrier band to the other end thereof. In addition, the PRB may be a resource block numbered within each BWP. A point A may indicate a common reference point for a resource block grid.

The BWP may be configured by a point A, an offset N^(start) _(BWP) from the point A, and a bandwidth N^(size) _(BWP). For example, the point A may be an external reference point of a PRB of a carrier in which a subcarrier 0 of all numerologies (e.g., all numerologies supported by a network on that carrier) is aligned. For example, the offset may be a PRB interval between a lowest subcarrier and the point A in a given numerology. For example, the bandwidth may be the number of PRBs in the given numerology.

Hereinafter, V2X or SL communication will be described.

A sidelink synchronization signal (SLSS) may include a primary sidelink synchronization signal (PSSS) and a secondary sidelink synchronization signal (SSSS), as an SL-specific sequence. The PSSS may be referred to as a sidelink primary synchronization signal (S-PSS), and the SSSS may be referred to as a sidelink secondary synchronization signal (S-SSS). For example, length-127 M-sequences may be used for the S-PSS, and length-127 gold sequences may be used for the S-SSS. For example, a UE may use the S-PSS for initial signal detection and for synchronization acquisition. For example, the UE may use the S-PSS and the S-SSS for acquisition of detailed synchronization and for detection of a synchronization signal ID.

A physical sidelink broadcast channel (PSBCH) may be a (broadcast) channel for transmitting default (system) information which must be first known by the UE before SL signal transmission/reception. For example, the default information may be information related to SLSS, a duplex mode (DM), a time division duplex (TDD) uplink/downlink (UL/DL) configuration, information related to a resource pool, a type of an application related to the SLSS, a subframe offset, broadcast information, or the like. For example, for evaluation of PSBCH performance, in NR V2X, a payload size of the PSBCH may be 56 bits including 24-bit cyclic redundancy check (CRC).

The S-PSS, the S-SSS, and the PSBCH may be included in a block format (e.g., SL synchronization signal (SS)/PSBCH block, hereinafter, sidelink-synchronization signal block (S-SSB)) supporting periodical transmission. The S-SSB may have the same numerology (i.e., SCS and CP length) as a physical sidelink control channel (PSCCH)/physical sidelink shared channel (PSSCH) in a carrier, and a transmission bandwidth may exist within a (pre-)configured sidelink (SL) BWP. For example, the S-SSB may have a bandwidth of 11 resource blocks (RBs). For example, the PSBCH may exist across 11 RBs. In addition, a frequency position of the S-SSB may be (pre-)configured. Accordingly, the UE does not have to perform hypothesis detection at frequency to discover the S-SSB in the carrier.

FIG. 7 shows a UE performing V2X or SL communication, based on an embodiment of the present disclosure. The embodiment of FIG. 7 may be combined with various embodiments of the present disclosure.

Referring to FIG. 7 , in V2X or SL communication, the term ‘UE’ may generally imply a UE of a user. However, if a network equipment such as a BS transmits/receives a signal according to a communication scheme between UEs, the BS may also be regarded as a sort of the UE. For example, a UE 1 may be a first apparatus 100, and a UE 2 may be a second apparatus 200.

For example, the UE 1 may select a resource unit corresponding to a specific resource in a resource pool which implies a set of series of resources. In addition, the UE 1 may transmit an SL signal by using the resource unit. For example, a resource pool in which the UE 1 is capable of transmitting a signal may be configured to the UE 2 which is a receiving UE, and the signal of the UE 1 may be detected in the resource pool.

Herein, if the UE 1 is within a connectivity range of the BS, the BS may inform the UE 1 of the resource pool. Otherwise, if the UE 1 is out of the connectivity range of the BS, another UE may inform the UE 1 of the resource pool, or the UE 1 may use a pre-configured resource pool.

In general, the resource pool may be configured in unit of a plurality of resources, and each UE may select a unit of one or a plurality of resources to use it in SL signal transmission thereof.

Hereinafter, resource allocation in SL will be described.

FIG. 8 shows a procedure of performing V2X or SL communication by a UE based on a transmission mode, based on an embodiment of the present disclosure. The embodiment of FIG. 8 may be combined with various embodiments of the present disclosure. In various embodiments of the present disclosure, the transmission mode may be called a mode or a resource allocation mode. Hereinafter, for convenience of explanation, in LTE, the transmission mode may be called an LTE transmission mode. In NR, the transmission mode may be called an NR resource allocation mode.

For example, (a) of FIG. 8 shows a UE operation related to an LTE transmission mode 1 or an LTE transmission mode 3. Alternatively, for example, (a) of FIG. 8 shows a UE operation related to an NR resource allocation mode 1. For example, the LTE transmission mode 1 may be applied to general SL communication, and the LTE transmission mode 3 may be applied to V2X communication.

For example, (b) of FIG. 8 shows a UE operation related to an LTE transmission mode 2 or an LTE transmission mode 4. Alternatively, for example, (b) of FIG. 8 shows a UE operation related to an NR resource allocation mode 2.

Referring to (a) of FIG. 8 , in the LTE transmission mode 1, the LTE transmission mode 3, or the NR resource allocation mode 1, a BS may schedule an SL resource to be used by the UE for SL transmission. For example, the BS may perform resource scheduling to a UE 1 through a PDCCH (e.g., downlink control information (DCI)) or RRC signaling (e.g., Configured Grant Type 1 or Configured Grant Type 2), and the UE 1 may perform V2X or SL communication with respect to a UE 2 according to the resource scheduling. For example, the UE 1 may transmit a sidelink control information (SCI) to the UE 2 through a physical sidelink control channel (PSCCH), and thereafter transmit data based on the SC to the UE 2 through a physical sidelink shared channel (PSSCH).

Referring to (b) of FIG. 8 , in the LTE transmission mode 2, the LTE transmission mode 4, or the NR resource allocation mode 2, the UE may determine an SL transmission resource within an SL resource configured by a BS/network or a pre-configured SL resource. For example, the configured SL resource or the pre-configured SL resource may be a resource pool. For example, the UE may autonomously select or schedule a resource for SL transmission. For example, the UE may perform SL communication by autonomously selecting a resource within a configured resource pool. For example, the UE may autonomously select a resource within a selective window by performing a sensing and resource (re)selection procedure. For example, the sensing may be performed in unit of subchannels. In addition, the UE 1 which has autonomously selected the resource within the resource pool may transmit the SCI to the UE 2 through a PSCCH, and thereafter may transmit data based on the SCI to the UE 2 through a PSSCH.

FIG. 9 shows three cast types, based on an embodiment of the present disclosure. The embodiment of FIG. 9 may be combined with various embodiments of the present disclosure. Specifically, (a) of FIG. 9 shows broadcast-type SL communication, (b) of FIG. 9 shows unicast type-SL communication, and (c) of FIG. 9 shows groupcast-type SL communication. In case of the unicast-type SL communication, a UE may perform one-to-one communication with respect to another UE. In case of the groupcast-type SL transmission, the UE may perform SL communication with respect to one or more UEs in a group to which the UE belongs. In various embodiments of the present disclosure, SL groupcast communication may be replaced with SL multicast communication, SL one-to-many communication, or the like.

Hereinafter, a hybrid automatic repeat request (HARQ) procedure will be described.

In case of SL unicast and groupcast, HARQ feedback and HARQ combining in the physical layer may be supported. For example, when a receiving UE operates in a resource allocation mode 1 or 2, the receiving UE may receive the PSSCH from a transmitting UE, and the receiving UE may transmit HARQ feedback for the PSSCH to the transmitting UE by using a sidelink feedback control information (SFCI) format through a physical sidelink feedback channel (PSFCH).

For example, the SL HARQ feedback may be enabled for unicast. In this case, in a non-code block group (non-CBG) operation, if the receiving UE decodes a PSCCH of which a target is the receiving UE and if the receiving UE successfully decodes a transport block related to the PSCCH, the receiving UE may generate HARQ-ACK. In addition, the receiving UE may transmit the HARQ-ACK to the transmitting UE. Otherwise, if the receiving UE cannot successfully decode the transport block after decoding the PSCCH of which the target is the receiving UE, the receiving UE may generate the HARQ-NACK. In addition, the receiving UE may transmit HARQ-NACK to the transmitting UE.

For example, the SL HARQ feedback may be enabled for groupcast. For example, in the non-CBG operation, two HARQ feedback options may be supported for groupcast.

(1) Groupcast option 1: After the receiving UE decodes the PSCCH of which the target is the receiving UE, if the receiving UE fails in decoding of a transport block related to the PSCCH, the receiving UE may transmit HARQ-NACK to the transmitting UE through a PSFCH. Otherwise, if the receiving UE decodes the PSCCH of which the target is the receiving UE and if the receiving UE successfully decodes the transport block related to the PSCCH, the receiving UE may not transmit the HARQ-ACK to the transmitting UE.

(2) Groupcast option 2: After the receiving UE decodes the PSCCH of which the target is the receiving UE, if the receiving UE fails in decoding of the transport block related to the PSCCH, the receiving UE may transmit HARQ-NACK to the transmitting UE through the PSFCH. In addition, if the receiving UE decodes the PSCCH of which the target is the receiving UE and if the receiving UE successfully decodes the transport block related to the PSCCH, the receiving UE may transmit the HARQ-ACK to the transmitting UE through the PSFCH.

For example, if the groupcast option 1 is used in the SL HARQ feedback, all UEs performing groupcast communication may share a PSFCH resource. For example, UEs belonging to the same group may transmit HARQ feedback by using the same PSFCH resource.

For example, if the groupcast option 2 is used in the SL HARQ feedback, each UE performing groupcast communication may use a different PSFCH resource for HARQ feedback transmission. For example, UEs belonging to the same group may transmit HARQ feedback by using different PSFCH resources.

For example, when the SL HARQ feedback is enabled for groupcast, the receiving UE may determine whether to transmit the HARQ feedback to the transmitting UE based on a transmission-reception (TX-RX) distance and/or Reference Signal Received Power (RSRP).

For example, in the groupcast option 1, in case of the TX-RX distance-based HARQ feedback, if the TX-RX distance is less than or equal to a communication range requirement, the receiving UE may transmit HARQ feedback for the PSSCH to the transmitting UE. Otherwise, if the TX-RX distance is greater than the communication range requirement, the receiving UE may not transmit the HARQ feedback for the PSSCH to the transmitting UE. For example, the transmitting UE may inform the receiving UE of a location of the transmitting UE through SCI related to the PSSCH. For example, the SCI related to the PSSCH may be second SCI. For example, the receiving UE may estimate or obtain the TX-RX distance based on a location of the receiving UE and the location of the transmitting UE. For example, the receiving UE may decode the SCI related to the PSSCH and thus may know the communication range requirement used in the PSSCH.

For example, in case of the resource allocation mode 1, a time (offset) between the PSFCH and the PSSCH may be configured or pre-configured. In case of unicast and groupcast, if retransmission is necessary on SL, this may be indicated to a BS by an in-coverage UE which uses the PUCCH. The transmitting UE may transmit an indication to a serving BS of the transmitting UE in a form of scheduling request (SR)/buffer status report (BSR), not a form of HARQ ACK/NACK. In addition, even if the BS does not receive the indication, the BS may schedule an SL retransmission resource to the UE. For example, in case of the resource allocation mode 2, a time (offset) between the PSFCH and the PSSCH may be configured or pre-configured.

For example, from a perspective of UE transmission in a carrier. TDM between the PSCCH/PSSCH and the PSFCH may be allowed for a PSFCH format for SL in a slot. For example, a sequence-based PSFCH format having a single symbol may be supported. Herein, the single symbol may not an AGC duration. For example, the sequence-based PSFCH format may be applied to unicast and groupcast.

For example, in a slot related to a resource pool, a PSFCH resource may be configured periodically as N slot durations, or may be pre-configured. For example, N may be configured as one or more values greater than or equal to 1. For example, N may be 1, 2, or 4. For example, HARQ feedback for transmission in a specific resource pool may be transmitted only through a PSFCH on the specific resource pool.

For example, if the transmitting UE transmits the PSSCH to the receiving UE across a slot #X to a slot #N, the receiving UE may transmit HARQ feedback for the PSSCH to the transmitting UE in a slot #(N+A). For example, the slot #(N+A) may include a PSFCH resource. Herein, for example, A may be a smallest integer greater than or equal to K. For example, K may be the number of logical slots. In this case, K may be the number of slots in a resource pool. Alternatively, for example, K may be the number of physical slots. In this case, K may be the number of slots inside or outside the resource pool.

For example, if the receiving UE transmits HARQ feedback on a PSFCH resource in response to one PSSCH transmitted by the transmitting UE to the receiving UE, the receiving UE may determine a frequency domain and/or code domain of the PSFCH resource based on an implicit mechanism in a configured resource pool. For example, the receiving UE may determine the frequency domain and/or code domain of the PSFCH resource, based on at least one of a slot index related to PSCCH/PSSCH/PSFCH, a sub-channel related to PSCCH/PSSCH, and/or an identifier for identifying each receiving UE in a group for HARQ feedback based on the groupcast option 2. Additionally/alternatively, for example, the receiving UE may determine the frequency domain and/or code domain of the PSFCH resource, based on at least one of SL RSRP, SINR, L1 source ID, and/or location information.

For example, if HARQ feedback transmission through the PSFCH of the UE and HARQ feedback reception through the PSFCH overlap, the UE may select any one of HARQ feedback transmission through the PSFCH and HARQ feedback reception through the PSFCH based on a priority rule. For example, the priority rule may be based on at least priority indication of the related PSCCH/PSSCH.

For example, if HARQ feedback transmission of a UE through a PSFCH for a plurality of UEs overlaps, the UE may select specific HARQ feedback transmission based on the priority rule. For example, the priority rule may be based on at least priority indication of the related PSCCH/PSSCH.

Meanwhile, in the present disclosure, a transmitting UE (i.e., TX UE) may be a UE which transmits data to a (target) receiving UE (i.e., RX UE). For example, the TX UE may be a UE which performs PSCCH transmission and/or PSSCH transmission. For example, the TX UE may be a UE which transmits SL CSI-RS(s) and/or an SL CSI report request indicator to the (target) RX UE. For example, the TX UE may be a UE which transmits (pre-defined) reference signal(s) (e.g., PSSCH demodulation reference signal(s) (DM-RS(s))) and/or an SL (L1) RSRP report request indicator to be used for SL (L1) RSRP measurement to the (target) RX UE(s). For example, the TX UE may be a UE which transmits (control) channel(s) (e.g., PSCCH, PSSCH, etc.) and/or reference signal(s) (e.g., DM-RS(s), CSI-RS(s), etc.) on the (control) channel(s) to be used for an SL radio link monitoring (RLM) operation and/or an SL radio link failure (RLF) operation of the (target) RX UE.

Meanwhile, in the present disclosure, a receiving UE (i.e., RX UE) may be a UE which transmits SL HARQ feedback to a transmitting UE (i.e., TX UE) based on whether decoding of data received from the TX UE is successful and/or whether detection/decoding of a PSCCH (related to PSSCH scheduling) transmitted by the TX UE is successful. For example, the RX UE may be a UE which performs SL CSI transmission to the TX UE based on SL CSI-RS(s) and/or an SL CSI report request indicator received from the TX UE. For example, the RX UE may be a UE which transmits, to the TX UE, an SL (L1) RSRP measurement value measured based on (pre-defined) reference signal(s) and/or an SL (L1) RSRP report request indicator received from the TX UE. For example, the RX UE may be a UE which transmits data of the RX UE to the TX UE. For example, the RX UE may be a UE which performs an SL RLM operation and/or an SL RLF operation based on a (pre-configured) (control) channel and/or reference signal(s) on the (control) channel received from the TX UE.

Meanwhile, in the present disclosure, a TX UE may transmit the entirety or part of information described below to the RX UE through SCI(s). Herein, for example, the TX UE may transmit the entirety or part of the information described below to the RX UE through a first SCI and/or a second SCI.

-   -   PSSCH (and/or PSCCH) related resource allocation information         (e.g., the location/number of time/frequency resources, resource         reservation information (e.g., period))     -   SL CSI report request indicator or SL (L1) RSRP (and/or SL (L1)         RSRQ and/or SL (L1) RSSI) report request indicator     -   SL CSI transmission indicator (or SL (L1) RSRP (and/or SL (L1)         RSRQ and/or SL (L1) RSSI) information transmission indicator))         (on a PSSCH)     -   Modulation and coding scheme (MCS) information     -   Transmit power information     -   L1 destination ID information and/or L1 source ID information     -   SL HARQ process ID information     -   New data indicator (NDI) information     -   Redundancy version (RV) information     -   (Transmission traffic/packet related) QoS information (e.g.,         priority information)     -   SL CSI-RS transmission indicator or information on the number of         antenna ports for (transmitted) SL CSI-RS     -   Location information of the TX UE or location (or distance         region) information of the target RX UE (for which SL HARQ         feedback is requested)     -   Reference signal (e.g., DM-RS, etc.) information related to         channel estimation and/or decoding of data to be transmitted         through a PSSCH. For example, the reference signal information         may be information related to a pattern of a (time-frequency)         mapping resource of DM-RS, rank information, antenna port index         information, information on the number of antenna ports, etc.

Meanwhile, in the present disclosure, for example, a PSCCH may be replaced/substituted with at least one of a SCI, a first SCI (1^(st)-stage SCI), and/or a second SCI (2^(nd)-stage SCI), or vice versa. For example, a SCI may be replaced/substituted with at least one of a PSCCH, a first SCI, and/or a second SCI, or vice versa. For example, a PSSCH may be replaced/substituted with a second SCI and/or a PSCCH, or vice versa.

Meanwhile, in the present disclosure, for example, if SCI configuration fields are divided into two groups in consideration of a (relatively) high SCI payload size, an SCI including a first SCI configuration field group may be referred to as a first SCI or a 1^(st) SCI, and an SCI including a second SCI configuration field group may be referred to as a second SCI or a 2^(nd) SCI. For example, the 1^(st) SCI and the 2^(nd) SCI may be transmitted through different channels. For example, the transmitting UE may transmit the first SCI to the receiving UE through the PSCCH. For example, the second SCI may be transmitted to the receiving UE through an (independent) PSCCH, or may be transmitted in a piggyback manner together with data through the PSSCH.

Meanwhile, in the present disclosure, for example, “configure/configured” or “define/defined” may refer to being (pre-)configured from a base station or a network. For example, “configure/configured” or “define/defined” may refer to being (pre-)configured for each resource pool from the base station or the network. For example, the base station or the network may transmit information related to “configuration” or “definition” to the UE. For example, the base station or the network may transmit information related to “configuration” or “definition” to the UE through pre-defined signaling. For example, the pre-defined signaling may include at least one of RRC signaling, MAC signaling, PHY signaling, and/or SIB.

Meanwhile, in the present disclosure, for example, “configure/configured” or “define/defined” may refer to being designated or configured through pre-configured signaling between UEs. For example, information related to “configuration” or “definition” may be transmitted or received pre-configured signaling between UEs. For example, the pre-defined signaling may include at least one of RRC signaling, MAC signaling, PHY signaling, and/or SIB.

Meanwhile, in the present disclosure, for example, RLF may be replaced/substituted with out-of-synch (OOS) and/or in-synch (IS), or vice versa.

Meanwhile, in the present disclosure, for example, a resource block (RB) may be replaced/substituted with a subcarrier, or vice versa. For example, a packet or a traffic may be replaced/substituted with a transport block (TB) or a medium access control protocol data unit (MAC PDU) according to a transmission layer, or vice versa. For example, a code block group (CBG) may be replaced/substituted with a TB, or vice versa. For example, a source ID may be replaced/substituted with a destination ID, or vice versa. For example, an L1 ID may be replaced/substituted with an L2 ID, or vice versa. For example, the L1 ID may be an L1 source ID or an L1 destination ID. For example, the L2 ID may be an L2 source ID or an L2 destination ID.

Meanwhile, in the present disclosure, for example, operation(s) of a TX UE to reserve/select/determine retransmission resource(s) may include operation(s) of the TX UE to reserve/select/determine potential retransmission resource(s) in which actual use is determined based on SL HARQ feedback information received from RX UE(s).

Meanwhile, in the present disclosure, a sub-selection window may be replaced/substituted with a selection window and/or a pre-configured number of resource sets within the selection window, or vice versa.

Meanwhile, in the present disclosure, SL MODE 1 may refer to a resource allocation method or a communication method in which a base station directly schedules SL transmission resource(s) for a TX UE through pre-defined signaling (e.g., DCI or RRC message). For example, SL MODE 2 may refer to a resource allocation method or a communication method in which a UE independently selects SL transmission resource(s) in a resource pool pre-configured or configured from a base station or a network. For example, a UE performing SL communication based on SL MODE 1 may be referred to as a MODE 1 UE or MODE 1 TX UE, and a UE performing SL communication based on SL MODE 2 may be referred to as a MODE 2 UE or MODE 2 TX UE.

Meanwhile, in the present disclosure, for example, a dynamic grant (DG) may be replaced/substituted with a configured grant (CG) and/or a semi-persistent scheduling (SPS) grant, or vice versa. For example, the DG may be replaced/substituted with a combination of the CG and the SPS grant, or vice versa. For example, the CG may include at least one of a configured grant (CG) type 1 and/or a configured grant (CG) type 2. For example, in the CG type 1, a grant may be provided by RRC signaling and may be stored as a configured grant. For example, in the CG type 2, a grant may be provided by a PDCCH, and may be stored or deleted as a configured grant based on L1 signaling indicating activation or deactivation of the grant. For example, in the CG type 1, a base station may allocate periodic resource(s) to a TX UE through an RRC message. For example, in the CG type 2, a base station may allocate periodic resource(s) to a TX UE through an RRC message, and the base station may dynamically activate or deactivate the periodic resource(s) through a DCI.

Meanwhile, in the present disclosure, a channel may be replaced/substituted with a signal, or vice versa. For example, transmission/reception of a channel may include transmission/reception of a signal. For example, transmission/reception of a signal may include transmission/reception of a channel. For example, cast may be replaced/substituted with at least one of unicast, groupcast, and/or broadcast, or vice versa. For example, a cast type may be replaced/substituted with at least one of unicast, groupcast, and/or broadcast, or vice versa. For example, the cast or the cast type may include unicast, groupcast and/or broadcast.

Meanwhile, in the present disclosure, a resource may be replaced/substituted with a slot or a symbol, or vice versa. For example, the resource may include a slot and/or a symbol.

Meanwhile, in the present disclosure, a priority may be replaced/substituted with at least one of logical channel prioritization (LCP), latency, reliability, minimum required communication range, prose per-packet priority (PPPP), sidelink radio bearer (SLRB), a QoS profile, a QoS parameter, and/or requirement, or vice versa.

Meanwhile, in the present disclosure, for example, for convenience of description, a (physical) channel used when a RX UE transmits at least one of the following information to a TX UE may be referred to as a PSFCH.

SL HARQ feedback, SL CSI, SL (L1) RSRP

Meanwhile, an SL discontinuous reception (DRX) operation may be supported for the UE. For example, for the SL DRX operation, the TX UE and the RX UE may obtain an SL DRX configuration. For example, the SL DRX configuration may be configured or pre-configured for the TX UE and the RX UE. For example, the TX UE may transmit the SL DRX configuration to the RX UE. For example, the SL DRX configuration may include at least one of information related to an SL DRX timer, information related to an SL DRX slot offset, information related to an SL DRX start offset, and/or information related to an SL DRX cycle.

For example, the SL DRX timer may include at least one of an SL DRX onduration timer, an SL DRX inactivity timer, an SL DRX retransmission timer, and/or an SL DRX HARQ RTT timer. For example, the SL DRX onduration timer may be the duration at the beginning of an SL DRX cycle. For example, the SL DRX inactivity timer may be the duration after the first slot of SCI reception in which an SCI indicates a new SL transmission for the MAC entity. For example, the SL DRX retransmission timer may be the maximum duration until an SL retransmission is received. For example, the SL DRX HARQ RTT timer may be the minimum duration before an SL HARQ retransmission is expected by the MAC entity. For example, the SL DRX retransmission timer and the SL DRX HARQ RTT timer may be configured per a sidelink process. For example, the SL DRX inactivity timer, the SL DRX retransmission timer, and the SL DRX HARQ RTT timer may not be applied for broadcast transmission. For example, the UE may start the SL DRX retransmission timer after the SL DRX HARQ RTT timer expires.

For example, the SL DRX slot offset may be a delay before the start of the SL DRX onduration timer. For example, the SL DRX start offset may be the slot where the SL DRX cycle starts.

For example, a time during which at least one of the SL DRX onduration timer, the SL DRX inactivity timer, and/or the SL DRX retransmission timer is running may be an active time. However, in various embodiments of the present disclosure, the active time is not limited to the time during which at least one of the SL DRX onduration timer, the SL DRX inactivity timer, and/or the SL DRX retransmission timer is running. For example, even if the SL DRX onduration timer, the SL DRX inactivity timer and the SL DRX retransmission timer are not running, the RX UE may operate in the active time, and the RX UE may monitor a PSCCH from the TX UE.

Meanwhile, when the UE #X (e.g., TX UE) and the UE #Y (e.g., RX UE) are performing unicast-based SL communication, the UE #X may simultaneously perform other SL communication with the UE #Z. Under this situation, when the UE #X determines/configures an SL DRX configuration of the UE #Y, the UE #X can minimize its own battery consumption by considering not only a generation pattern of a packet to be transmitted to the UE #Y but also a generation pattern of a packet to be transmitted to the UE #Z. For example, the UE #X may perform packet transmission to the UE #Y and the UE #Z as continuously as possible after turning on its RF, and through this, the UE #X can minimize its own battery consumption. Meanwhile, for example, after the UE #X establishes a unicast link with the UE #Y, if packet transmission from the UE #X to the UE #Y is performed based on an SL DRX configuration related to information such as a TX profile (and/or a QoS profile) related to a packet, not performed based on an SL DRX configuration related to the unicast link, battery consumption minimization in terms of the UE #X (described above) may not be achieved.

Based on various embodiments of the present disclosure, a method for a UE to perform SL communication based on an SL DRX configuration and an apparatus supporting the same are proposed. In the present disclosure, for example, a TX profile may be referred to as a profile or an SL DRX profile. For example, the TX profile, the profile, or the SL DRX profile may indicate/represent SL DRX ON (i.e., SL DRX compatible), or may indicate/represent SL DRX OFF (i.e., SL DRX incompatible).

For example, it may be (pre-)configured that data transmission/reception assuming that SL DRX is applied should be performed (e.g., referred to as SL DRX ON) or data transmission/reception assuming that SL DRX is not applied should be performed (e.g., referred to as SL DRX OFF). For example, it may be (pre-)configured for the TX UE and/or the RX UE that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. For example, it may be (pre-)configured for each service type that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. For example, it may be (pre-)configured for each QoS requirement/profile that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. For example, it may be (pre-)configured for each radio bearer that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. For example, it may be (pre-)configured for each logical channel that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. For example, it may be (pre-)configured for each release that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. For example, it may be (pre-)configured for each QoS flow ID that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. For example, it may be (pre-)configured for each (L2) source ID that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. For example, it may be (pre-)configured for each (L2) destination ID that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. For example, it may be (pre-)configured for each SL session/link that data transmission/reception assuming that SL DRX is applied should be performed or data transmission/reception assuming that SL DRX is not applied should be performed. In the present disclosure, for convenience of description, such configuration information may be referred to as an SL DRX profile, a TX profile, or a profile.

Herein, for example, in the case of the TX UE, when an upper layer (e.g., V2X layer) of the TX UE transfers a packet to a lower layer (e.g., PHY layer, MAC layer, RLC layer, RRC layer, PDCP layer, SDAP layer), an SL DRX profile may also be transferred together. In this case, if the SL DRX profile is set to SL DRX ON, the TX UE may perform packet transmission, by selecting candidate resource(s) within an SL DRX active time applied by the RX UE interested in the related service type. On the other hand, if the SL DRX profile is set to SL DRX OFF, the TX UE may select candidate resource(s) related to packet transmission, by assuming that the RX UE interested in the related service type is always in a wake-up state. In addition, for example, in the case of the RX UE, an upper laver of the RX UE may transfer an SL DRX profile for a service type of interest of the RX UE to a lower layer. In this case, if the SL DRX profile is set to SL DRX ON, the RX UE may wake-up within an SL DRX active time and perform the related packet reception operation. On the other hand, if the SL DRX profile is set to SL DRX OFF, the RX UE may always wake-up and perform the related packet reception operation.

For example, based on the (some) proposed methods below, a method for more efficiently managing power consumption of the RX UE is provided. Herein, for example, the proposed rule of the present disclosure may be limitedly applied to a (pre-configured) cast type (e.g., unicast). For example, the proposed rule of the present disclosure may be limitedly applied to a (pre-configured) service type. For example, the proposed rule of the present disclosure may be limitedly applied to a (pre-configured) priority. For example, the proposed rule of the present disclosure may be limitedly applied to a (pre-configured) QoS requirement/profile. For example, the proposed rule of the present disclosure may be limitedly applied to a (pre-configured) radio bearer. For example, the proposed rule of the present disclosure may be limitedly applied to a (pre-configured) logical channel. For example, the proposed rule of the present disclosure may be limitedly applied to a (pre-configured) release. For example, the proposed rule of the present disclosure may be limitedly applied to a (pre-configured) QoS flow ID. For example, the term “(a pair/combination of)(L2) source ID and/or (L2) destination ID” (and/or the term “SL session/link”) used in the present disclosure can be extend to (and/or replaced with) a service type. For example, the term “(a pair/combination of) (L2) source ID and/or (L2) destination ID” (and/or the term “SL session/link”) used in the present disclosure can be extend to (and/or replaced with) a cast type. For example, the term “(a pair/combination of) (L2) source ID and/or (L2) destination ID” (and/or the term “SL session/link”) used in the present disclosure can be extend to (and/or replaced with) a priority. For example, the term “(a pair/combination of) (L2) source ID and/or (L2) destination ID” (and/or the term “SL session/link”) used in the present disclosure can be extend to (and/or replaced with) a QoS requirement/profile. For example, the term “(a pair/combination of) (L2) source ID and/or (L2) destination ID” (and/or the term “SL session/link”) used in the present disclosure can be extend to (and/or replaced with) a radio bearer. For example, the term “(a pair/combination of) (L2) source ID and/or (L2) destination ID” (and/or the term “SL session/link”) used in the present disclosure can be extend to (and/or replaced with) a logical channel. For example, the term “(a pair/combination of) (L2) source ID and/or (L2) destination ID” (and/or the term “SL session/link”) used in the present disclosure can be extend to (and/or replaced with) a release. For example, the term “(a pair/combination of) (L2) source ID and/or (L2) destination ID” (and/or the term “SL session/link”) used in the present disclosure can be extend to (and/or replaced with) a QoS flow ID. For example, the term “(a pair/combination of) (L2) source ID and/or (L2) destination ID” (and/or the term “SL session/link”) used in the present disclosure can be extend to (and/or replaced with) an SL session/link.

Based on an embodiment of the present disclosure, for example, for (a pair/combination of) a (L2) source ID and/or a (L2) destination ID, an SL DRX configuration (hereinafter referred to as ONGO_SLDRX) (configured by the TX UE based on the request/assistance information received from the RX UE) may be present/configured. In this case, even if the SL DRX profile is set to SL DRX OFF, in the case of a packet transmitted/received through an SL session/link related to (the pair/combination of) the (L2) source ID and/or the (L2) destination ID, the TX UE may be configured to select transmission resource(s) based on an SL DRX active time duration of ONGO_SLDRX, and the RX UE may be configured to perform a reception operation based on the SL DRX active time duration of ONGO_SLDRX. And/or, if the SL DRX active time duration of ONGO_SLDRX and the other (inactive time) duration exist (within the remaining PDB), the UE may be configured to select transmission resource(s) within the active time duration as a (relatively) high priority. Herein, for example, if the rule is applied, SL DRX ON/OFF may be finally determined based on whether (the pair/combination of) the (L2) source ID and/or the (L2) destination ID-specific ONGO_SLDRX is presented or not (not based on the SL DRX profile), it may be interpreted that ONGO_SLDRX overrides the SL DRX profile. In addition, for example, under the above example situation, if the SL DRX profile of the packet transmitted/received through the SL session/link related to (the pair/combination of) the (L2) source ID and/or the (L2) destination ID is set to SL DRX ON, transmission resource selection and reception operations may be performed based on the SL DRX active time duration of ONGO_SLDRX.

For example, if the above-described rule is applied, the UE may be configured not to start/operate the SL DRX timer if a packet related to the SL DRX profile set to SL DRX OFF is transmitted/received in the SL DRX active time duration of ONGO_SLDRX. On the other hand, for example, if a packet related to the SL DRX profile set to SL DRX ON is transmitted/received in the SL DRX active time duration of ONGO_SLDRX, the UE may be configured to start/operate the SL DRX timer. In addition, for example, in order for the RX UE to determine whether the SL DRX profile related to the packet transmitted by the TX UE is SL DRX ON or SL DRX OFF (even if PSSCH decoding fails), related information may be transmitted through pre-defined signaling (e.g., PSCCH, SCI, etc.). Or, for example, if the above-described rule is applied, the UE may be configured to start/operate the SL DRX timer in all cases where the packet related to the SL DRX profile set to SL DRX ON and the packet related to the SL DRX profile set to SL DRX OFF are transmitted/received in the SL DRX active time duration of ONGO_SLDRX.

For example, if the above-described rule is applied, if the TX UE transmits a packet related to the SL DRX profile set to SL DRX OFF, the TX UE may select resource(s) (e.g., all resources for initial transmission and required number of retransmissions) from among candidate resources within an active time duration, currently running, of ONGO_SLDRX (hereinafter, RUN_ACTTIME), and the TX UE may perform packet transmission based on the selected resource(s). On the other hand, for example, if the TX UE transmits a packet related to the SL DRX profile set to SL DRX ON, the TX UE may select resource(s)(e.g., all resources for initial transmission and required number of retransmissions) from among candidate resources in RUN_ACTTIME of ONGO_SLDRX and candidate resources within an active time to be extended due to resource(s) to be selected within RUN_ACTTIME, and the TX UE may perform packet transmission based on the selected resource(s).

Based on an embodiment of the present disclosure, for example, a service type with the same characteristic for whether SL DRX is applied/required may be configured (limitedly) for each SL session/link related to (a pair/combination of) a (L2) source ID and/or a (L2) destination ID. For example, a QoS profile with the same characteristic for whether SL DRX is applied/required may be configured (limitedly) for each SL session/link related to (a pair/combination of) a (L2) source ID and/or a (L2) destination ID. For example, a radio bearer with the same characteristic for whether SL DRX is applied/required may be configured (limitedly) for each SL session/link related to (a pair/combination of) a (L2) source ID and/or a (L2) destination ID. For example, a logical channel with the same characteristic for whether SL DRX is applied/required may be configured (limitedly) for each SL session/link related to (a pair/combination of) a (L2) source ID and/or a (L2) destination ID. For example, a release with the same characteristic for whether SL DRX is applied/required may be configured (limitedly) for each SL session/link related to (a pair/combination of) a (L2) source ID and/or a (L2) destination ID. For example, a QoS flow ID with the same characteristic for whether SL DRX is applied/required may be configured (limitedly) for each SL session/link related to (a pair/combination of) a (L2) source ID and/or a (L2) destination ID.

Herein, for example, if the corresponding rule is applied, when a characteristic of whether SL DRX is applied/required for the currently operating SL session/link is different from a characteristic of whether SL DRX is applied/required for a service type to be added, it may be interpreted that an SL session/link related to (a pair/combination of) a new (L2) source ID and/or a new (L2) destination ID (different from the existing value) should be created. For example, if the corresponding rule is applied, when a characteristic of whether SL DRX is applied/required for the currently operating SL session/link is different from a characteristic of whether SL DRX is applied/required for a QoS profile to be added, it may be interpreted that an SL session/link related to (a pair/combination of) a new (L2) source ID and/or a new (L2) destination ID (different from the existing value) should be created. For example, if the corresponding rule is applied, when a characteristic of whether SL DRX is applied/required for the currently operating SL session/link is different from a characteristic of whether SL DRX is applied/required for a radio bearer to be added, it may be interpreted that an SL session/link related to (a pair/combination of) a new (L2) source ID and/or a new (L2) destination ID (different from the existing value) should be created. For example, if the corresponding rule is applied, when a characteristic of whether SL DRX is applied/required for the currently operating SL session/link is different from a characteristic of whether SL DRX is applied/required for a logical channel to be added, it may be interpreted that an SL session/link related to (a pair/combination of) a new (L2) source ID and/or a new (L2) destination ID (different from the existing value) should be created. For example, if the corresponding rule is applied, when a characteristic of whether SL DRX is applied/required for the currently operating SL session/link is different from a characteristic of whether SL DRX is applied/required for a release to be added, it may be interpreted that an SL session/link related to (a pair/combination of) a new (L2) source ID and/or a new (L2) destination ID (different from the existing value) should be created. For example, if the corresponding rule is applied, when a characteristic of whether SL DRX is applied/required for the currently operating SL session/link is different from a characteristic of whether SL DRX is applied/required for a QoS flow ID to be added, it may be interpreted that an SL session/link related to (a pair/combination of) a new (L2) source ID and/or a new (L2) destination ID (different from the existing value) should be created.

For example, if SL DRX is not applied/required for a service type to be added, the service type may be added to an (currently operating) SL session/link which includes/supports both a service type for which SL DRX is applied/required and a service type for which SL DRX is not applied/required, but the service type may not be added to an (currently operating) SL session/link which only includes/supports a service type for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a QoS profile to be added, the QoS profile may be added to an (currently operating) SL session/link which includes/supports both a QoS profile for which SL DRX is applied/required and a QoS profile for which SL DRX is not applied/required, but the QoS profile may not be added to an (currently operating) SL session/link which only includes/supports a QoS profile for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a radio bearer to be added, the radio bearer may be added to an (currently operating) SL session/link which includes/supports both a radio bearer for which SL DRX is applied/required and a radio bearer for which SL DRX is not applied/required, but the radio bearer may not be added to an (currently operating) SL session/link which only includes/supports a radio bearer for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a logical channel to be added, the logical channel may be added to an (currently operating) SL session/link which includes/supports both a logical channel for which SL DRX is applied/required and a logical channel for which SL DRX is not applied/required, but the logical channel may not be added to an (currently operating) SL session/link which only includes/supports a logical channel for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a release to be added, the release may be added to an (currently operating) SL session/link which includes/supports both a release for which SL DRX is applied/required and a release for which SL DRX is not applied/required, but the release may not be added to an (currently operating) SL session/link which only includes/supports a release for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a QoS flow ID to be added, the QoS flow ID may be added to an (currently operating) SL session/link which includes/supports both a QoS flow ID for which SL DRX is applied/required and a QoS flow ID for which SL DRX is not applied/required, but the QoS flow ID may not be added to an (currently operating) SL session/link which only includes/supports a QoS flow ID for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a service type to be added, the service type may be added to an (currently operating) SL session/link which includes/supports both a service type for which SL DRX is applied/required and a service type for which SL DRX is not applied/required, and the service type may be added to an (currently operating) SL session/link which only includes/supports a service type for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a QoS profile to be added, the QoS profile may be added to an (currently operating) SL session/link which includes/supports both a QoS profile for which SL DRX is applied/required and a QoS profile for which SL DRX is not applied/required, and the QoS profile may be added to an (currently operating) SL session/link which only includes/supports a QoS profile for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a radio bearer to be added, the radio bearer may be added to an (currently operating) SL session/link which includes/supports both a radio bearer for which SL DRX is applied/required and a radio bearer for which SL DRX is not applied/required, and the radio bearer may be added to an (currently operating) SL session/link which only includes/supports a radio bearer for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a logical channel to be added, the logical channel may be added to an (currently operating) SL session/link which includes/supports both a logical channel for which SL DRX is applied/required and a logical channel for which SL DRX is not applied/required, and the logical channel may be added to an (currently operating) SL session/link which only includes/supports a logical channel for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a release to be added, the release may be added to an (currently operating) SL session/link which includes/supports both a release for which SL DRX is applied/required and a release for which SL DRX is not applied/required, and the release may be added to an (currently operating) SL session/link which only includes/supports a release for which SL DRX is applied/required.

For example, if SL DRX is not applied/required for a QoS flow ID to be added, the QoS flow ID may be added to an (currently operating) SL session/link which includes/supports both a QoS flow ID for which SL DRX is applied/required and a QoS flow ID for which SL DRX is not applied/required, and the QoS flow ID may be added to an (currently operating) SL session/link which only includes/supports a QoS flow ID for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a service type to be added, the service type may not be added to an (currently operating) SL session/link which includes/supports both a service type for which SL DRX is applied/required and a service type for which SL DRX is not applied/required, but the service type may be added to an (currently operating) SL session/link which only includes/supports a service type for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a QoS profile to be added, the QoS profile may not be added to an (currently operating) SL session/link which includes/supports both a QoS profile for which SL DRX is applied/required and a QoS profile for which SL DRX is not applied/required, but the QoS profile may be added to an (currently operating) SL session/link which only includes/supports a QoS profile for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a radio bearer to be added, the radio bearer may not be added to an (currently operating) SL session/link which includes/supports both a radio bearer for which SL DRX is applied/required and a radio bearer for which SL DRX is not applied/required, but the radio bearer may be added to an (currently operating) SL session/link which only includes/supports a radio bearer for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a logical channel to be added, the logical channel may not be added to an (currently operating) SL session/link which includes/supports both a logical channel for which SL DRX is applied/required and a logical channel for which SL DRX is not applied/required, but the logical channel may be added to an (currently operating) SL session/link which only includes/supports a logical channel for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a release to be added, the release may not be added to an (currently operating) SL session/link which includes/supports both a release for which SL DRX is applied/required and a release for which SL DRX is not applied/required, but the release may be added to an (currently operating) SL session/link which only includes/supports a release for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a QoS flow ID to be added, the QoS flow ID may not be added to an (currently operating) SL session/link which includes/supports both a QoS flow ID for which SL DRX is applied/required and a QoS flow ID for which SL DRX is not applied/required, but the QoS flow ID may be added to an (currently operating) SL session/link which only includes/supports a QoS flow ID for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a service type to be added, the service type may be added to an (currently operating) SL session/link which includes/supports both a service type for which SL DRX is applied/required and a service type for which SL DRX is not applied/required, and the service type may be added to an (currently operating) SL session/link which only includes/supports a service type for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a QoS profile to be added, the QoS profile may be added to an (currently operating) SL session/link which includes/supports both a QoS profile for which SL DRX is applied/required and a QoS profile for which SL DRX is not applied/required, and the QoS profile may be added to an (currently operating) SL session/link which only includes/supports a QoS profile for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a radio bearer to be added, the radio bearer may be added to an (currently operating) SL session/link which includes/supports both a radio bearer for which SL DRX is applied/required and a radio bearer for which SL DRX is not applied/required, and the radio bearer may be added to an (currently operating) SL session/link which only includes/supports a radio bearer for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a logical channel to be added, the logical channel may be added to an (currently operating) SL session/link which includes/supports both a logical channel for which SL DRX is applied/required and a logical channel for which SL DRX is not applied/required, and the logical channel may be added to an (currently operating) SL session/link which only includes/supports a logical channel for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a release to be added, the release may be added to an (currently operating) SL session/link which includes/supports both a release for which SL DRX is applied/required and a release for which SL DRX is not applied/required, and the release may be added to an (currently operating) SL session/link which only includes/supports a release for which SL DRX is applied/required.

For example, if SL DRX is applied/required for a QoS flow ID to be added, the QoS flow ID may be added to an (currently operating) SL session/link which includes/supports both a QoS flow ID for which SL DRX is applied/required and a QoS flow ID for which SL DRX is not applied/required, and the QoS flow ID may be added to an (currently operating) SL session/link which only includes/supports a QoS flow ID for which SL DRX is applied/required.

For example, whether the rule is applied (and/or the parameter value related to the proposed method/rule) may be configured/allowed specifically (or differently or independently) for at least one of a service type, a (LCH or service) priority, a QoS requirement (e.g., latency, reliability, minimum communication range), a PQI parameter. HARQ feedback enabled LCH/MAC PDU (transmission), HARQ feedback disabled LCH/MAC PDU (transmission), a CBR measurement value of a resource pool, a SL cast type (e.g., unicast, groupcast, broadcast), a SL groupcast HARQ feedback option (e.g., NACK only feedback, ACK/NACK feedback, NACK only feedback based on TX-RX distance), a SL mode 1 CG type (e.g., SL CG type 1 or SL CG type 2), a SL mode type (e.g., mode 1 or mode 2), a resource pool, whether a PSFCH resource is configured in a resource pool, a source (L2) ID, a destination (L2) ID, a PC5 RRC connection link, a SL link, a connection state (with a base station) (e.g., RRC CONNECTED state. IDLE state. INACTIVE state), a SL HARQ process (ID), whether to perform SL DRX operation (of TX UE or RX UE), whether a UE is a power saving (TX or RX) UE, a case in which PSFCH TX and PSFCH RX (and/or a plurality of PSFCH TXs (exceeding UE capability)) overlap (and/or a case in which PSFCH TX (and/or PSFCH RX) is skipped) (from a specific UE perspective), and/or a case in which the RX UE actually (successfully) receives PSCCH (and/or PSSCH) (re)transmission from the TX UE. In addition, in the present disclosure, the term “configured/configuration (or designated/designation)” can be extended/interpreted to/as that the base station informs the UE through a pre-defined (physical layer or higher layer) channel/signal (e.g., SIB, RRC, MAC CE) (and/or being provided through pre-configuration and/or that the UE informs other UEs through a pre-defined (physical layer or higher layer) channel/signal (e.g., SL MAC CE, PC5 RRC)). In addition, in the present disclosure, the term “PSFCH” can be extended/interpreted to/as (NR or LTE) PSSCH (and/or (NR or LTE) PSCCH) (and/or (NR or LTE) SL SSB (and/or UL channel/signal)). In addition, the proposed methods of the present disclosure can be used in combination with each other (as a new type of manner).

Based on various embodiments of the present disclosure, after the UE #X (e.g., TX UE) establishes a unicast link with the UE #Y (e.g., RX UE), packet transmission from the UE #X to the UE #Y may be performed based on an SL DRX configuration associated with the unicast link, regardless of the related TX profile (and/or QoS profile). For example, before a unicast link is established between the UE #X and the UE #Y, a default SL DRX configuration may be applied to packet transmission to which a QoS profile is not mapped (based on the TX profile representing ON or compatible, received from a higher layer). On the other hand, for example, after the unicast link is established between the UE #X and the UE #Y, an SL DRX configuration associated with the unicast link may be applied for packet transmission with the same characteristic. Through this, when the UE #X simultaneously performs SL communication with other UE(s) as well as unicast-based SL communication with the UE #Y, the UE #X can minimize its own battery consumption (by performing packet transmission to the UE #Y based on the SL DRX configuration associated with the unicast link, after establishing the unicast link with the UE #Y).

FIG. 10 shows a method for a first device to perform wireless communication, based on an embodiment of the present disclosure. The embodiment of FIG. 10 may be combined with various embodiments of the present disclosure.

Referring to FIG. 10 , in step S1010, the first device may obtain a default sidelink (SL) discontinuous reception (DRX) configuration. In step S1020, the first device may obtain a profile representing whether SL DRX is compatible. In step S1030, the first device may perform first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible. In step S1040, the first device may establish a PC5 radio resource control (RRC) connection with a second device. In step S1050, the first device may obtain an SL DRX configuration. In step S1060, the first device may transmit, to the second device, information related to the SL DRX configuration. In step S1070, the first device may perform, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.

Additionally, for example, the first device may select a first SL resource within an active time related to the default SL DRX configuration, based on the profile representing that the SL DRX is compatible. For example, the first SL transmission may be performed based on the first SL resource.

Additionally, for example, the first device may determine that the second device interested in the first SL transmission does not perform an SL DRX operation, based on the profile representing that the SL DRX is incompatible. Additionally, for example, the first device may select a first SL resource without considering the default SL DRX configuration. For example, the first SL transmission may be performed based on the first SL resource.

Additionally, for example, the first device may select a second SL resource within an active time related to the SL DRX configuration, based on the PC5 RRC connection being established between the first device and the second device. For example, the second SL transmission may be performed based on the second SL resource. For example, based on the PC5 RRC connection being established between the first device and the second device, the profile may not be considered in the second SL transmission by the first device.

For example, obtaining the profile representing whether SL DRX is compatible may include: transferring, by a higher layer of the first device, the profile to a lower layer of the first device, before establishing the PC5 RRC connection with the second device. For example, after establishing the PC5 RRC connection with the second device, a higher layer of the first device may not be allowed to transfer the profile to a lower layer of the first device.

For example, the SL DRX configuration may be configured for a pair of a source identifier (ID) and a destination ID.

Additionally, for example, the first device may receive assistance information from the second device. For example, the SL DRX configuration may be configured for a pair of a source ID and a destination ID based on the assistance information.

For example, the PC5 RRC connection may only support transmission for which an SL DRX operation is required. For example, the second SL transmission may include transmission for which the SL DRX operation is required and may not include transmission for which the SL DRX operation is not required. For example, the first device may not be allowed to perform third SL transmission for which the SL DRX operation is not required through the PC5 RRC connection based on the SL DRX configuration.

For example, the PC5 RRC connection may support transmission for which an SL DRX operation is required and transmission for which the SL DRX operation is not required. For example, the second SL transmission may include the transmission for which the SL DRX operation is required or the transmission for which the SL DRX operation is not required.

For example, the first SL transmission may include transmission of information for establishing the PC5 RRC connection, and the default SL DRX configuration may include information related to a first SL DRX cycle and information related to a timer for a first SL DRX active time, and the SL DRX configuration may include information related to a second SL DRX cycle and information related to a timer for a second SL DRX active time.

The proposed method can be applied to the device(s) based on various embodiments of the present disclosure. First, the processor 102 of the first device 100 may obtain a default sidelink (SL) discontinuous reception (DRX) configuration. In addition, the processor 102 of the first device 100 may obtain a profile representing whether SL DRX is compatible. In addition, the processor 102 of the first device 100 may control the transceiver 106 to perform first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible. In addition, the processor 102 of the first device 100 may establish a PC5 radio resource control (RRC) connection with a second device. In addition, the processor 102 of the first device 100 may obtain an SL DRX configuration. In addition, the processor 102 of the first device 100 may control the transceiver 106 to transmit, to the second device, information related to the SL DRX configuration. In addition, the processor 102 of the first device 100 may control the transceiver 106 to perform, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.

Based on an embodiment of the present disclosure, a first device adapted to perform wireless communication may be provided. For example, the first device may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible: control the one or more transceivers to perform first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible, establish a PC5 radio resource control (RRC) connection with a second device; obtain an SL DRX configuration; control the one or more transceivers to transmit, to the second device, information related to the SL DRX configuration; and control the one or more transceivers to perform, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.

Based on an embodiment of the present disclosure, a processing device adapted to control a first device performing wireless communication may be provided. For example, the processing device may comprise: one or more processors; and one or more memories operably connected to the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible; perform first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establish a PC5 radio resource control (RRC) connection with a second device; obtain an SL DRX configuration; transmit, to the second device, information related to the SL DRX configuration; and perform, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.

Based on an embodiment of the present disclosure, a non-transitory computer readable storage medium storing instructions may be provided. For example, the instructions, when executed, may cause a first device to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible; perform first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establish a PC5 radio resource control (RRC) connection with a second device; obtain an SL DRX configuration; transmit, to the second device, information related to the SL DRX configuration; and perform, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.

FIG. 11 shows a method for a second device to perform wireless communication, based on an embodiment of the present disclosure. The embodiment of FIG. 11 may be combined with various embodiments of the present disclosure.

Referring to FIG. 11 , in step S1110, the second device may obtain a default sidelink (SL) discontinuous reception (DRX) configuration. In step S1120, the second device may obtain a profile representing whether SL DRX is compatible. In step S1130, the second device may perform first SL reception based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible. In step S1140, the second device may establish a PC5 radio resource control (RRC) connection with a first device. In step S1150, the second device may obtain an SL DRX configuration. In step S1160, the second device may receive, from the first device, information related to the SL DRX configuration. In step S1170, the second device may perform, from the first device, second SL reception based on the SL DRX configuration, regardless of the profile.

The proposed method can be applied to the device(s) based on various embodiments of the present disclosure. First, the processor 202 of the second device 200 may obtain a default sidelink (SL) discontinuous reception (DRX) configuration. In addition, the processor 202 of the second device 200 may obtain a profile representing whether SL DRX is compatible. In addition, the processor 202 of the second device 200 may control the transceiver 206 to perform first SL reception based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible. In addition, the processor 202 of the second device 200 may establish a PC5 radio resource control (RRC) connection with a first device. In addition, the processor 202 of the second device 200 may obtain an SL DRX configuration. In addition, the processor 202 of the second device 200 may control the transceiver 206 to receive, from the first device, information related to the SL DRX configuration. In addition, the processor 202 of the second device 200 may control the transceiver 206 to perform, from the first device, second SL reception based on the SL DRX configuration, regardless of the profile.

Based on an embodiment of the present disclosure, a second device adapted to perform wireless communication may be provided. For example, the second device may comprise: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers. For example, the one or more processors may execute the instructions to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible; control the one or more transceivers to perform first SL reception based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establish a PC5 radio resource control (RRC) connection with a first device; obtain an SL DRX configuration; control the one or more transceivers to receive, from the first device, information related to the SL DRX configuration; and control the one or more transceivers to perform, from the first device, second SL reception based on the SL DRX configuration, regardless of the profile.

Based on an embodiment of the present disclosure, a processing device adapted to control a second device performing wireless communication may be provided. For example, the processing device may comprise: one or more processors; and one or more memories operably connected to the one or more processors and storing instructions. For example, the one or more processors may execute the instructions to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible; perform first SL reception based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establish a PC5 radio resource control (RRC) connection with a first device; obtain an SL DRX configuration; receive, from the first device, information related to the SL DRX configuration; and perform, from the first device, second SL reception based on the SL DRX configuration, regardless of the profile.

Based on an embodiment of the present disclosure, a non-transitory computer readable storage medium storing instructions may be provided. For example, the instructions, when executed, may cause a second device to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible; perform first SL reception based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establish a PC5 radio resource control (RRC) connection with a first device; obtain an SL DRX configuration; receive, from the first device, information related to the SL DRX configuration; and perform, from the first device, second SL reception based on the SL DRX configuration, regardless of the profile.

Various embodiments of the present disclosure may be combined with each other.

Hereinafter, device(s) to which various embodiments of the present disclosure can be applied will be described.

The various descriptions, functions, procedures, proposals, methods, and/or operational flowcharts of the present disclosure described in this document may be applied to, without being limited to, a variety of fields requiring wireless communication/connection (e.g., 5G) between devices.

Hereinafter, a description will be given in more detail with reference to the drawings. In the following drawings/description, the same reference symbols may denote the same or corresponding hardware blocks, software blocks, or functional blocks unless described otherwise.

FIG. 12 shows a communication system 1, based on an embodiment of the present disclosure.

Referring to FIG. 12 , a communication system 1 to which various embodiments of the present disclosure are applied includes wireless devices, Base Stations (BSs), and a network. Herein, the wireless devices represent devices performing communication using Radio Access Technology (RAT) (e.g., 5G New RAT (NR)) or Long-Term Evolution (LTE)) and may be referred to as communication/radio/5G devices. The wireless devices may include, without being limited to, a robot 100 a, vehicles 100 b-1 and 100 b-2, an eXtended Reality (XR) device 100 c, a hand-held device 100 d, a home appliance 100 e, an Internet of Things (IoT) device 100 f, and an Artificial Intelligence (AI) device/server 400. For example, the vehicles may include a vehicle having a wireless communication function, an autonomous vehicle, and a vehicle capable of performing communication between vehicles. Herein, the vehicles may include an Unmanned Aerial Vehicle (UAV) (e.g., a drone). The XR device may include an Augmented Reality (AR)/Virtual Reality (VR)/Mixed Reality (MR) device and may be implemented in the form of a Head-Mounted Device (HMD), a Head-Up Display (HUD) mounted in a vehicle, a television, a smartphone, a computer, a wearable device, a home appliance device, a digital signage, a vehicle, a robot, etc. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), and a computer (e.g., a notebook). The home appliance may include a TV, a refrigerator, and a washing machine. The IoT device may include a sensor and a smartmeter. For example, the BSs and the network may be implemented as wireless devices and a specific wireless device 200 a may operate as a BS/network node with respect to other wireless devices.

Here, wireless communication technology implemented in wireless devices 100 a to 100 f of the present disclosure may include Narrowband Internet of Things for low-power communication in addition to LTE, NR, and 6G. In this case, for example, NB-IoT technology may be an example of Low Power Wide Area Network (LPWAN) technology and may be implemented as standards such as LTE Cat NB1, and/or LTE Cat NB2, and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100 a to 100 f of the present disclosure may perform communication based on LTE-M technology. In this case, as an example, the LTE-M technology may be an example of the LPWAN and may be called by various names including enhanced Machine Type Communication (eMTC), and the like. For example, the LTE-M technology may be implemented as at least any one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-Bandwidth Limited (non-BL), 5) LTE-MTC, 6) LTE Machine Type Communication, and/or 7) LTE M. and is not limited to the name described above. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100 a to 100 f of the present disclosure may include at least one of Bluetooth, Low Power Wide Area Network (LPWAN), and ZigBee considering the low-power communication, and is not limited to the name described above. As an example, the ZigBee technology may generate personal area networks (PAN) related to small/low-power digital communication based on various standards including IEEE 802.15.4, and the like, and may be called by various names.

The wireless devices 100 a to 100 f may be connected to the network 300 via the BSs 200. An AI technology may be applied to the wireless devices 100 a to 100 f and the wireless devices 100 a to 100 f may be connected to the AI server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100 a to 100 f may communicate with each other through the BSs 200/network 300, the wireless devices 100 a to 100 f may perform direct communication (e.g., sidelink communication) with each other without passing through the BSs/network. For example, the vehicles 100 b-1 and 100 b-2 may perform direct communication (e.g. Vehicle-to-Vehicle (V2V)/Vehicle-to-everything (V2X) communication). The IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., sensors) or other wireless devices 100 a to 100 f.

Wireless communication/connections 150 a, 150 b, or 150 c may be established between the wireless devices 100 a to 100 f/BS 200, or BS 200/BS 200. Herein, the wireless communication/connections may be established through various RATs (e.g., 5G NR) such as uplink/downlink communication 150 a, sidelink communication 150 b (or, D2D communication), or inter BS communication (e.g. relay, Integrated Access Backhaul (JAB)). The wireless devices and the BSs/the wireless devices may transmit/receive radio signals to/from each other through the wireless communication/connections 150 a and 150 b. For example, the wireless communication/connections 150 a and 150 b may transmit/receive signals through various physical channels. To this end, at least a part of various configuration information configuring processes, various signal processing processes (e.g., channel encoding/decoding, modulation/demodulation, and resource mapping/demapping), and resource allocating processes, for transmitting/receiving radio signals, may be performed based on the various proposals of the present disclosure.

FIG. 13 shows wireless devices, based on an embodiment of the present disclosure.

Referring to FIG. 13 , a first wireless device 100 and a second wireless device 200 may transmit radio signals through a variety of RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to {the wireless device 100 x and the BS 200} and/or {the wireless device 100 x and the wireless device 100 x} of FIG. 12 .

The first wireless device 100 may include one or more processors 102 and one or more memories 104 and additionally further include one or more transceivers 106 and/or one or more antennas 108. The processor(s) 102 may control the memory(s) 104 and/or the transceiver(s) 106 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 102 may process information within the memory(s) 104 to generate first information/signals and then transmit radio signals including the first information/signals through the transceiver(s) 106. The processor(s) 102 may receive radio signals including second information/signals through the transceiver 106 and then store information obtained by processing the second information/signals in the memory(s) 104. The memory(s) 104 may be connected to the processor(s) 102 and may store a variety of information related to operations of the processor(s) 102. For example, the memory(s) 104 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 102 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 102 and the memory(s) 104 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 106 may be connected to the processor(s) 102 and transmit and/or receive radio signals through one or more antennas 108. Each of the transceiver(s) 106 may include a transmitter and/or a receiver. The transceiver(s) 106 may be interchangeably used with Radio Frequency (RF) unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

The second wireless device 200 may include one or more processors 202 and one or more memories 204 and additionally further include one or more transceivers 206 and/or one or more antennas 208. The processor(s) 202 may control the memory(s) 204 and/or the transceiver(s) 206 and may be configured to implement the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. For example, the processor(s) 202 may process information within the memory(s) 204 to generate third information/signals and then transmit radio signals including the third information/signals through the transceiver(s)206. The processor(s) 202 may receive radio signals including fourth information/signals through the transceiver(s) 106 and then store information obtained by processing the fourth information/signals in the memory(s) 204. The memory(s) 204 may be connected to the processor(s) 202 and may store a variety of information related to operations of the processor(s) 202. For example, the memory(s) 204 may store software code including commands for performing a part or the entirety of processes controlled by the processor(s) 202 or for performing the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. Herein, the processor(s) 202 and the memory(s) 204 may be a part of a communication modem/circuit/chip designed to implement RAT (e.g., LTE or NR). The transceiver(s) 206 may be connected to the processor(s) 202 and transmit and/or receive radio signals through one or more antennas 208. Each of the transceiver(s) 206 may include a transmitter and/or a receiver. The transceiver(s) 206 may be interchangeably used with RF unit(s). In the present disclosure, the wireless device may represent a communication modem/circuit/chip.

Hereinafter, hardware elements of the wireless devices 100 and 200 will be described more specifically. One or more protocol layers may be implemented by, without being limited to, one or more processors 102 and 202. For example, the one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY. MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102 and 202 may generate one or more Protocol Data Units (PDUs) and/or one or more Service Data Unit (SDUs) according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document. The one or more processors 102 and 202 may generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document and provide the generated signals to the one or more transceivers 106 and 206. The one or more processors 102 and 202 may receive the signals (e.g., baseband signals) from the one or more transceivers 106 and 206 and acquire the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document.

The one or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. The one or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software and the firmware or software may be configured to include the modules, procedures, or functions. Firmware or software configured to perform the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be included in the one or more processors 102 and 202 or stored in the one or more memories 104 and 204 so as to be driven by the one or more processors 102 and 202. The descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, commands, and/or a set of commands.

The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, code, instructions, and/or commands. The one or more memories 104 and 204 may be configured by Read-Only Memories (ROMs), Random Access Memories (RAMs), Electrically Erasable Programmable Read-Only Memories (EPROMs), flash memories, hard drives, registers, cash memories, computer-readable storage media, and/or combinations thereof. The one or more memories 104 and 204 may be located at the interior and/or exterior of the one or more processors 102 and 202. The one or more memories 104 and 204 may be connected to the one or more processors 102 and 202 through various technologies such as wired or wireless connection.

The one or more transceivers 106 and 206 may transmit user data, control information, and/or radio signals/channels, mentioned in the methods and/or operational flowcharts of this document, to one or more other devices. The one or more transceivers 106 and 206 may receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, from one or more other devices. For example, the one or more transceivers 106 and 206 may be connected to the one or more processors 102 and 202 and transmit and receive radio signals. For example, the one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may transmit user data, control information, or radio signals to one or more other devices. The one or more processors 102 and 202 may perform control so that the one or more transceivers 106 and 206 may receive user data, control information, or radio signals from one or more other devices. The one or more transceivers 106 and 206 may be connected to the one or more antennas 108 and 208 and the one or more transceivers 106 and 206 may be configured to transmit and receive user data, control information, and/or radio signals/channels, mentioned in the descriptions, functions, procedures, proposals, methods, and/or operational flowcharts disclosed in this document, through the one or more antennas 108 and 208. In this document, the one or more antennas may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). The one or more transceivers 106 and 206 may convert received radio signals/channels etc. from RF band signals into baseband signals in order to process received user data, control information, radio signals/channels, etc. using the one or more processors 102 and 202. The one or more transceivers 106 and 206 may convert the user data, control information, radio signals/channels, etc. processed using the one or more processors 102 and 202 from the base band signals into the RF band signals. To this end, the one or more transceivers 106 and 206 may include (analog) oscillators and/or filters.

FIG. 14 shows a signal process circuit for a transmission signal, based on an embodiment of the present disclosure.

Referring to FIG. 14 , a signal processing circuit 1000 may include scramblers 1010, modulators 1020, a layer mapper 1030, a precoder 1040, resource mappers 1050, and signal generators 1060. An operation/function of FIG. 14 may be performed, without being limited to, the processors 102 and 202 and/or the transceivers 106 and 206 of FIG. 13 . Hardware elements of FIG. 14 may be implemented by the processors 102 and 202 and/or the transceivers 106 and 206 of FIG. 13 . For example, blocks 1010 to 1060 may be implemented by the processors 102 and 202 of FIG. 13 . Alternatively, the blocks 1010 to 1050 may be implemented by the processors 102 and 202 of FIG. 13 and the block 1060 may be implemented by the transceivers 106 and 206 of FIG. 13 .

Codewords may be converted into radio signals via the signal processing circuit 1000 of FIG. 14 . Herein, the codewords are encoded bit sequences of information blocks. The information blocks may include transport blocks (e.g., a UL-SCH transport block, a DL-SCH transport block). The radio signals may be transmitted through various physical channels (e.g., a PUSCH and a PDSCH).

Specifically, the codewords may be converted into scrambled bit sequences by the scramblers 1010. Scramble sequences used for scrambling may be generated based on an initialization value, and the initialization value may include ID information of a wireless device. The scrambled bit sequences may be modulated to modulation symbol sequences by the modulators 1020. A modulation scheme may include pi/2-Binary Phase Shift Keying (pi/2-BPSK), m-Phase Shift Keying (m-PSK), and m-Quadrature Amplitude Modulation (m-QAM). Complex modulation symbol sequences may be mapped to one or more transport layers by the layer mapper 1030. Modulation symbols of each transport layer may be mapped (precoded) to corresponding antenna port(s) by the precoder 1040. Outputs z of the precoder 1040 may be obtained by multiplying outputs y of the layer mapper 1030 by an N*M precoding matrix W. Herein, N is the number of antenna ports and M is the number of transport layers. The precoder 1040 may perform precoding after performing transform precoding (e.g., DFT) for complex modulation symbols. Alternatively, the precoder 1040 may perform precoding without performing transform precoding.

The resource mappers 1050 may map modulation symbols of each antenna port to time-frequency resources. The time-frequency resources may include a plurality of symbols (e.g., a CP-OFDMA symbols and DFT-s-OFDMA symbols) in the time domain and a plurality of subcarriers in the frequency domain. The signal generators 1060 may generate radio signals from the mapped modulation symbols and the generated radio signals may be transmitted to other devices through each antenna. For this purpose, the signal generators 1060 may include Inverse Fast Fourier Transform (IFFT) modules, Cyclic Prefix (CP) inserters, Digital-to-Analog Converters (DACs), and frequency up-converters.

Signal processing procedures for a signal received in the wireless device may be configured in a reverse manner of the signal processing procedures 1010 to 1060 of FIG. 14 . For example, the wireless devices (e.g., 100 and 200 of FIG. 13 ) may receive radio signals from the exterior through the antenna ports/transceivers. The received radio signals may be converted into baseband signals through signal restorers. To this end, the signal restorers may include frequency downlink converters, Analog-to-Digital Converters (ADCs). CP remover, and Fast Fourier Transform (FFT) modules. Next, the baseband signals may be restored to codewords through a resource demapping procedure, a postcoding procedure, a demodulation processor, and a descrambling procedure. The codewords may be restored to original information blocks through decoding. Therefore, a signal processing circuit (not illustrated) for a reception signal may include signal restorers, resource demappers, a postcoder, demodulators, descramblers, and decoders.

FIG. 15 shows another example of a wireless device, based on an embodiment of the present disclosure. The wireless device may be implemented in various forms according to a use-case/service (refer to FIG. 12 ).

Referring to FIG. 15 , wireless devices 100 and 200 may correspond to the wireless devices 100 and 200 of FIG. 13 and may be configured by various elements, components, units/portions, and/or modules. For example, each of the wireless devices 100 and 200 may include a communication unit 110, a control unit 120, a memory unit 130, and additional components 140. The communication unit may include a communication circuit 112 and transceiver(s) 114. For example, the communication circuit 112 may include the one or more processors 102 and 202 and/or the one or more memories 104 and 204 of FIG. 13 . For example, the transceiver(s) 114 may include the one or more transceivers 106 and 206 and/or the one or more antennas 108 and 208 of FIG. 13 . The control unit 120 is electrically connected to the communication unit 110, the memory 130, and the additional components 140 and controls overall operation of the wireless devices. For example, the control unit 120 may control an electric/mechanical operation of the wireless device based on programs/code/commands/information stored in the memory unit 130. The control unit 120 may transmit the information stored in the memory unit 130 to the exterior (e.g., other communication devices) via the communication unit 110 through a wireless/wired interface or store, in the memory unit 130, information received through the wireless/wired interface from the exterior (e.g., other communication devices) via the communication unit 110.

The additional components 140 may be variously configured according to types of wireless devices. For example, the additional components 140 may include at least one of a power unit/battery, input/output (I/O) unit, a driving unit, and a computing unit. The wireless device may be implemented in the form of, without being limited to, the robot (100 a of FIG. 12), the vehicles (100 b-1 and 100 b-2 of FIG. 12 ), the XR device (100 c of FIG. 12 ), the hand-held device (100 d of FIG. 12 ), the home appliance (100 e of FIG. 12 ), the IoT device (100 f of FIG. 12 ), a digital broadcast terminal, a hologram device, a public safety device, an MTC device, a medicine device, a fintech device (or a finance device), a security device, a climate/environment device, the AI server/device (400 of FIG. 12 ), the BSs (200 of FIG. 12 ), a network node, etc. The wireless device may be used in a mobile or fixed place according to a use-example/service.

In FIG. 15 , the entirety of the various elements, components, units/portions, and/or modules in the wireless devices 100 and 200 may be connected to each other through a wired interface or at least a part thereof may be wirelessly connected through the communication unit 110. For example, in each of the wireless devices 100 and 200, the control unit 120 and the communication unit 110 may be connected by wire and the control unit 120 and first units (e.g., 130 and 140) may be wirelessly connected through the communication unit 110. Each element, component, unit/portion, and/or module within the wireless devices 100 and 200 may further include one or more elements. For example, the control unit 120 may be configured by a set of one or more processors. As an example, the control unit 120 may be configured by a set of a communication control processor, an application processor, an Electronic Control Unit (ECU), a graphical processing unit, and a memory control processor. As another example, the memory 130 may be configured by a Random Access Memory (RAM), a Dynamic RAM (DRAM), a Read Only Memory (ROM)), a flash memory, a volatile memory, a non-volatile memory, and/or a combination thereof.

Hereinafter, an example of implementing FIG. 15 will be described in detail with reference to the drawings.

FIG. 16 shows a hand-held device, based on an embodiment of the present disclosure. The hand-held device may include a smartphone, a smartpad, a wearable device (e.g., a smartwatch or a smartglasses), or a portable computer (e.g., a notebook). The hand-held device may be referred to as a mobile station (MS), a user terminal (UT), a Mobile Subscriber Station (MSS), a Subscriber Station (SS), an Advanced Mobile Station (AMS), or a Wireless Terminal (WT).

Referring to FIG. 16 , a hand-held device 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a memory unit 130, a power supply unit 140 a, an interface unit 140 b, and an I/O unit 140 c. The antenna unit 108 may be configured as a part of the communication unit 110. Blocks 110 to 130/140 a to 140 c correspond to the blocks 110 to 130/140 of FIG. 15 , respectively.

The communication unit 110 may transmit and receive signals (e.g., data and control signals) to and from other wireless devices or BSs. The control unit 120 may perform various operations by controlling constituent elements of the hand-held device 100. The control unit 120 may include an Application Processor (AP). The memory unit 130 may store data/parameters/programs/code/commands needed to drive the hand-held device 100. The memory unit 130 may store input/output data/information. The power supply unit 140 a may supply power to the hand-held device 100 and include a wired/wireless charging circuit, a battery, etc. The interface unit 140 b may support connection of the hand-held device 100 to other external devices. The interface unit 140 b may include various ports (e.g., an audio I/O port and a video I/O port) for connection with external devices. The I/O unit 140 c may input or output video information/signals, audio information/signals, data, and/or information input by a user. The I/O unit 140 c may include a camera, a microphone, a user input unit, a display unit 140 d, a speaker, and/or a haptic module.

As an example, in the case of data communication, the I/O unit 140 c may acquire information/signals (e.g., touch, text, voice, images, or video) input by a user and the acquired information/signals may be stored in the memory unit 130. The communication unit 110 may convert the information/signals stored in the memory into radio signals and transmit the converted radio signals to other wireless devices directly or to a BS. The communication unit 110 may receive radio signals from other wireless devices or the BS and then restore the received radio signals into original information/signals. The restored information/signals may be stored in the memory unit 130 and may be output as various types (e.g., text, voice, images, video, or haptic) through the I/O unit 140 c.

FIG. 17 shows a vehicle or an autonomous vehicle, based on an embodiment of the present disclosure. The vehicle or autonomous vehicle may be implemented by a mobile robot, a car, a train, a manned/unmanned Aerial Vehicle (AV), a ship, etc.

Referring to FIG. 17 , a vehicle or autonomous vehicle 100 may include an antenna unit 108, a communication unit 110, a control unit 120, a driving unit 140 a, a power supply unit 140 b, a sensor unit 140 c, and an autonomous driving unit 140 d. The antenna unit 108 may be configured as a part of the communication unit 110. The blocks 110/130/140 a to 140 d correspond to the blocks 110/130/140 of FIG. 15 , respectively.

The communication unit 110 may transmit and receive signals (e.g., data and control signals) to and from external devices such as other vehicles, BSs (e.g., gNBs and road side units), and servers. The control unit 120 may perform various operations by controlling elements of the vehicle or the autonomous vehicle 100. The control unit 120 may include an Electronic Control Unit (ECU). The driving unit 140 a may cause the vehicle or the autonomous vehicle 100 to drive on a road. The driving unit 140 a may include an engine, a motor, a powertrain, a wheel, a brake, a steering device, etc. The power supply unit 140 b may supply power to the vehicle or the autonomous vehicle 100 and include a wired/wireless charging circuit, a battery, etc. The sensor unit 140 c may acquire a vehicle state, ambient environment information, user information, etc. The sensor unit 140 c may include an Inertial Measurement Unit (IMU) sensor, a collision sensor, a wheel sensor, a speed sensor, a slope sensor, a weight sensor, a heading sensor, a position module, a vehicle forward/backward sensor, a battery sensor, a fuel sensor, a tire sensor, a steering sensor, a temperature sensor, a humidity sensor, an ultrasonic sensor, an illumination sensor, a pedal position sensor, etc. The autonomous driving unit 140 d may implement technology for maintaining a lane on which a vehicle is driving, technology for automatically adjusting speed, such as adaptive cruise control, technology for autonomously driving along a determined path, technology for driving by automatically setting a path if a destination is set, and the like.

For example, the communication unit 110 may receive map data, traffic information data, etc. from an external server. The autonomous driving unit 140 d may generate an autonomous driving path and a driving plan from the obtained data. The control unit 120 may control the driving unit 140 a such that the vehicle or the autonomous vehicle 100 may move along the autonomous driving path according to the driving plan (e.g., speed/direction control). In the middle of autonomous driving, the communication unit 110 may aperiodically/periodically acquire recent traffic information data from the external server and acquire surrounding traffic information data from neighboring vehicles. In the middle of autonomous driving, the sensor unit 140 c may obtain a vehicle state and/or surrounding environment information. The autonomous driving unit 140 d may update the autonomous driving path and the driving plan based on the newly obtained data/information. The communication unit 110 may transfer information about a vehicle position, the autonomous driving path, and/or the driving plan to the external server. The external server may predict traffic information data using AI technology, etc., based on the information collected from vehicles or autonomous vehicles and provide the predicted traffic information data to the vehicles or the autonomous vehicles.

Claims in the present description can be combined in a various way. For instance, technical features in method claims of the present description can be combined to be implemented or performed in an apparatus, and technical features in apparatus claims can be combined to be implemented or performed in a method. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in an apparatus. Further, technical features in method claim(s) and apparatus claim(s) can be combined to be implemented or performed in a method. 

1-20. (canceled)
 21. A method for performing wireless communication by a first device, the method comprising: obtaining a default sidelink (SL) discontinuous reception (DRX) configuration; obtaining a profile representing whether SL DRX is compatible; performing first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establishing a PC5 radio resource control (RRC) connection with a second device; obtaining an SL DRX configuration; transmitting, to the second device, information related to the SL DRX configuration; and performing, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.
 22. The method of claim 21, further comprising: selecting a first SL resource within an active time related to the default SL DRX configuration, based on the profile representing that the SL DRX is compatible, wherein the first SL transmission is performed based on the first SL resource.
 23. The method of claim 21, further comprising: determining that the second device interested in the first SL transmission does not perform an SL DRX operation, based on the profile representing that the SL DRX is incompatible; and selecting a first SL resource without considering the default SL DRX configuration, wherein the first SL transmission is performed based on the first SL resource.
 24. The method of claim 21, further comprising: selecting a second SL resource within an active time related to the SL DRX configuration, based on the PC5 RRC connection being established between the first device and the second device, wherein the second SL transmission is performed based on the second SL resource.
 25. The method of claim 24, wherein, based on the PC5 RRC connection being established between the first device and the second device, the profile is not considered in the second SL transmission by the first device.
 26. The method of claim 21, wherein obtaining the profile representing whether SL DRX is compatible includes: transferring, by a higher layer of the first device, the profile to a lower layer of the first device, before establishing the PC5 RRC connection with the second device.
 27. The method of claim 21, wherein, after establishing the PC5 RRC connection with the second device, a higher layer of the first device is not allowed to transfer the profile to a lower layer of the first device.
 28. The method of claim 21, wherein the SL DRX configuration is configured for a pair of a source identifier (ID) and a destination ID.
 29. The method of claim 21, further comprising: receiving assistance information from the second device, wherein the SL DRX configuration is configured for a pair of a source ID and a destination ID based on the assistance information.
 30. The method of claim 21, wherein the PC5 RRC connection only supports transmission for which an SL DRX operation is required.
 31. The method of claim 30, wherein the second SL transmission includes transmission for which the SL DRX operation is required and does not include transmission for which the SL DRX operation is not required, and wherein the first device is not allowed to perform third SL transmission for which the SL DRX operation is not required through the PC5 RRC connection based on the SL DRX configuration.
 32. The method of claim 21, wherein the PC5 RRC connection supports transmission for which an SL DRX operation is required and transmission for which the SL DRX operation is not required, and wherein the second SL transmission includes the transmission for which the SL DRX operation is required or the transmission for which the SL DRX operation is not required.
 33. The method of claim 21, wherein the first SL transmission includes transmission of information for establishing the PC5 RRC connection, wherein the default SL DRX configuration includes information related to a first SL DRX cycle and information related to a timer for a first SL DRX active time, and wherein the SL DRX configuration includes information related to a second SL DRX cycle and information related to a timer for a second SL DRX active time.
 34. A first device adapted to perform wireless communication, the first device comprising: one or more memories storing instructions; one or more transceivers; and one or more processors connected to the one or more memories and the one or more transceivers, wherein the one or more processors execute the instructions to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible; control the one or more transceivers to perform first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establish a PC5 radio resource control (RRC) connection with a second device; obtain an SL DRX configuration; control the one or more transceivers to transmit, to the second device, information related to the SL DRX configuration; and control the one or more transceivers to perform, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile.
 35. The first device of claim 34, wherein the one or more processors further execute the instructions to: select a first SL resource within an active time related to the default SL DRX configuration, based on the profile representing that the SL DRX is compatible, wherein the first SL transmission is performed based on the first SL resource.
 36. The first device of claim 34, wherein the one or more processors further execute the instructions to: determine that the second device interested in the first SL transmission does not perform an SL DRX operation, based on the profile representing that the SL DRX is incompatible, and select a first SL resource without considering the default SL DRX configuration, wherein the first SL transmission is performed based on the first SL resource.
 37. The first device of claim 34, wherein the one or more processors further execute the instructions to: select a second SL resource within an active time related to the SL DRX configuration, based on the PC5 RRC connection being established between the first device and the second device, wherein the second SL transmission is performed based on the second SL resource.
 38. The first device of claim 37, wherein, based on the PC5 RRC connection being established between the first device and the second device, the profile is not considered in the second SL transmission by the first device.
 39. The first device of claim 34, wherein obtaining the profile representing whether SL DRX is compatible includes: transferring, by a higher layer of the first device, the profile to a lower layer of the first device, before establishing the PC5 RRC connection with the second device.
 40. A processing device adapted to control a first device performing wireless communication, the processing device comprising: one or more processors; and one or more memories operably connected to the one or more processors and storing instructions, wherein the one or more processors execute the instructions to: obtain a default sidelink (SL) discontinuous reception (DRX) configuration; obtain a profile representing whether SL DRX is compatible; perform first SL transmission based on the default SL DRX configuration, based on the profile representing that the SL DRX is compatible; establish a PC5 radio resource control (RRC) connection with a second device; obtain an SL DRX configuration; transmit, to the second device, information related to the SL DRX configuration; and perform, to the second device, second SL transmission based on the SL DRX configuration, regardless of the profile. 